Process lifecycle
States, transitions and the order of a create.
States
state | Meaning |
|---|---|
PROCESS_STATE_CREATED | Not finished. Includes a Journey waiting for the person |
PROCESS_STATE_FINISHED | Has an outcome, including a negative revalidation or an inconclusive identification |
PROCESS_STATE_FAILED | Processing failed, the person cancelled, or the create was interrupted |
A capture the person cancels is answered as PROCESS_STATE_FAILED.
FINISHED is not "approved"
Read the outcome in data: humanToken.status, liveness.value and humanTokenMatch. A finished revalidation with humanTokenMatch other than "true" is a finished process that does not match.
Finished and failed are final.
Order of a create
- Human Plugin validates the request. Errors here store nothing and send nothing.
- It stores the process and starts it. This step is not cancelled if your client disconnects, and takes at most 30 seconds.
- It stores the result, then computes the person's intelligence for
data.ndocs.
A process is never started twice.
When the outcome is uncertain
If the process cannot be confirmed in time, Human Plugin stores it as failed and answers 502. To try again, create a new process with a new correlationId.
If the container stops during a create, a later GET marks the process failed once the create can no longer be running (about 70 seconds).
See Errors and retries for retry guidance.