Skip to main content
Scrive

The Scrive eID Hub task that polls verifications in progress

The Scrive eID Hub: poll verifications in progress task runs every 10 minutes and is active as soon as you install the module: on each run it asks Scrive again about verifications in New or Started and cancels the ones that have been open too long. If it does nothing for a given verification, the conditions that keep it out of the run are listed below.

FlexigoTech · Editor in charge: Víctor Gómez · Updated 5 November 2026

Key facts

Module
Scrive
Versions
Odoo 17, 18, 19 and 20
Checked
in the connector's source code, version 17.0 and 20.0 · against the sources linked at the end
Reading time
5 min

What it is and where you see its effect

The scheduled task Scrive eID Hub: poll verifications in progress exists in every published branch of the module: Odoo 17.0, 18.0, 19.0 and 20.0. It runs every 10 minutes and is active on install. In Odoo 17.0 it repeats without end.

You see its effect in the verifications, which open from Scrive › Configuration › eID Hub Verifications. The Configuration part of the menu needs the Manager permission and the Scrive part needs User; if you lack one, you do not see that part.

The Status field of each verification appears on its form and in the Identity Verifications list, with the values New, Started, Failed and Complete. The form also shows, read-only, the Scrive Transaction ID, which the module fills in, not you; its help reads: The UUID assigned by Scrive eID Hub once the transaction is created.

Code-generated diagram, not an Odoo screen: the scheduled task that runs every 10 minutes and is active on install, and below it the menu for eID Hub verifications
Code-generated diagram based on the module's published code (not an Odoo screenshot): the task, every 10 minutes, active on install in Odoo 17.0, 18.0, 19.0 and 20.0, and the verifications menu. The labels in the diagram are in English.
Code-generated diagram, not an Odoo screen: the task name in Spanish, German, French, Italian and Portuguese
Code-generated diagram based on the module's published translations (not an Odoo screenshot): the task name according to the language of Odoo. In English it is Scrive eID Hub: poll verifications in progress.
Odoo + Scrive: see who signed, get the sealed PDF
Video: Odoo + Scrive: see who signed, get the sealed PDF

Timeline of one run

These are the moments of a run, in the order the Odoo 20.0 code goes through them.

  1. On install The task is active and scheduled every 10 minutes; in Odoo 17.0 it repeats without end.
  1. Every 10 minutes, at the start First it checks that there is a FlexigoTech Cloud service. If there is none, it calls nothing at Scrive and closes nothing: the verifications wait for the service to come back, and the run is noted in the server log.
  1. Then, the search It takes the verifications in New or Started, oldest first by creation date, up to a maximum per run. Left out are those of an eID account with its kill switch on or without its token saved in FlexigoTech Cloud. That filter is part of the search itself, so those rows do not take up room in the batch.
  1. Row by row, the check Each verification is handled in isolation: a failure in one does not drag down the next. If it has a Scrive Transaction ID, the module asks Scrive for its status and stores it. If Scrive answers Failed or Complete, the verification is treated as over and the access link hosted at Scrive is cleared. If it answers Complete, the module evaluates whether the identity returned matches the contact's.
  1. If Scrive does not answer properly When the check ends in an API or configuration error, it is noted in the server log and the error text is kept on the verification (unless its identity data has already been purged). The code then carries on with the time check for that same row.
  1. Then, the time limit If after the check it is still New or Started and has been open longer than allowed since its creation, it is cancelled. With a transaction ID and an account whose kill switch is not on, the module may ask Scrive to cancel it. If that cancellation fails with an API or configuration error, it is noted and the row is closed in Odoo anyway. Without a transaction ID, it is closed in Odoo without calling Scrive.
  1. On closing The verification goes to Failed, its access link is cleared and The identity verification was not completed in time; it was cancelled automatically. is stored as the reason.
  1. If FlexigoTech Cloud does not let the call through The run stops there, nothing is marked and the remaining rows wait for the next run. If it was cancelling, the verification is not closed either.
  1. Any other failure on a row It is noted in the server log and the run carries on with the others.
  1. At the end You see the result in the Status column of the Identity Verifications list.

Why the task exists

According to the code comments, Scrive used to be queried only when the browser came back and from the completion webhook. That webhook is off by default and needs Scrive to allow the URL first. An abandoned or slow verification therefore stayed in New or Started for ever. The code gives Swedish BankID on the same device in iOS as an example, where the browser can come back before the app has finished.

So each run does two things, in this order: it re-checks every verification in progress and then cancels and closes the ones that have been open too long, so that their access link stops being usable.

What to check if it does nothing

Go through these conditions, which come straight from the code:

  • FlexigoTech Cloud service. Without the service, the run calls nothing at Scrive and closes nothing. The same happens if FlexigoTech Cloud pauses during the run: it stops and the remaining rows wait.
  • eID account. If its kill switch is on, or its token is not saved in FlexigoTech Cloud, its verifications do not enter the search and are neither checked nor closed.
  • Status. Only verifications in New or Started are looked at. One in Failed or Complete is no longer touched.
  • Transaction ID. Without a Scrive Transaction ID, the task checks nothing; for that verification, the task only closes it once the allowed time has passed.
  • Order and batch. Work goes from oldest to newest, with a maximum per run. If many verifications are in progress, a recent one may have to wait for a later run.
  • Version. The task is in Odoo 17.0, 18.0, 19.0 and 20.0, with the same frequency.

Cost and help

The module is a one-off payment per version and needs the FlexigoTech Cloud subscription, Connector plan: €49/month or €490/year excluding VAT, up to 3 platform accounts. The connection goes through FlexigoTech Cloud, which stores the credentials encrypted. Without a subscription, or with the service suspended, what the subscription provides stops; your data stays in your Odoo. It is published on Odoo Apps for 17.0, 18.0, 19.0 and 20.0: see the listing or the module page.

FlexigoTech implements Odoo 17, 18, 19 and 20 and builds custom connectors and integrations, in case you want to review how this flow fits into your installation.

Keep reading

What the Send button of Scrive Connector does, step by stepWhat the Send button of Scrive Connector does in Odoo: what it checks, what it creates, where it takes you next and which messages can stop it.Scrive Connector: «Callbacks can only be triggered for sent documents.»When the callbacks error shows up in Scrive Connector for Odoo, which condition triggers it (document state and Scrive ID) and how to fix it.The «Days must be between 1 and 365.» message in Scrive ConnectorWhen Scrive Connector shows «Days must be between 1 and 365.», what the code checks when you press Apply, and how to fix it.
Checked in the connector's source code (version 17.0 and 20.0) and the linked sources

Sources