Status Workflow Diagram
The following diagram represents the status workflow from the creation of a signature/interaction until its conclusion or irreversible error.

The status are:
SUBSCRIBED: As soon as the signature/interaction has been created, it will have this state. Awaiting for the signer to land on thefUrl.POD_FAILED: When the signer accesses thefUrl, the system may try to reserve a POD to host the signing environment; this happens only in the forensic workflows. At this point, a fatal, unrecoverable error may happen that forbids the POD initialisation, and the signature/interaction will transit to this state. Although with very low probability, this may occur and thus was modelled. FINALOURL_FAILED: In case of Webpage or Data interactions, the system proxies or redirects the signer to a specified URL calledOUrl. If this action fails, generally due to external factors to our systems, for instance,OUrlis responding with an error, the interaction transits to this state. FINALREJECTED: For the Document signatures, one can specify that the signature is rejectable. If the signer then rejects the signature, the signature will transit to this state. FINALCONCLUDING: When the signer finishes the signing process, the system will start concluding the signature/interaction, creating a PDF, forensic evidence, and so on. And so while doing this, the signature/interaction will transi to this state.CONCLUDING_FAILED: While concluding the signatures or interactions, some errors may happen, for example, while calling external services like PDF or XML timestamping and signing. In this case the signature/interaction will transit to this state, and automatic retries will take place to try and get out of this state.CONCLUDING_FAILED_PERM: There are cases where the error during the conclusion phase is not recoverable. In this case, the signature/interaction will transit to this state. FINALCONCLUDED: When the signature/interaction was concluded and everything was generated correctly, the signature/interaction will transit to this state. FINAL
The error status happens with really low probability. To give you some numbers, since our service is up from 2018, the probability of a falling in:
POD_FAILEDis 0.003OURL_FAILEDis 0.001 β considering these are mostly the responsibility of the API callerCONCLUDING_FAILEDis 0.00007 β most of which were automatically recovered.CONCLUDING_FAILED_PERMis 0.000002