Transaction Status "Pending"
The main status "Pending" encompasses two important substatuses that indicate the current phase of a transaction.
Pending (Status 10: Pending) is the most common; it means the documents are ready and awaiting signature from at least one signer. The transaction details and audit trail provide insight into the invitation's dispatch status and who still needs to sign, after which the signing links can optionally be manually re-shared.
Pending (Status 20: In progress) indicates that the Signhost server is actively processing the transaction, for example, immediately after the transaction is created or after a signature has been placed. Although this process is normally very brief, a status that remains "In progress" for longer than 5 minutes may indicate a problem with the transaction.
In short, when you create a new signing request, a request is sent to the Signhost server for processing. During this process, the transaction receives the status "Pending (Status 20: In progress)". But what exactly does this mean, and what can you do if this status persists longer than expected?
What does 'In progress' (Status 20) mean?
This status indicates that your request is being processed by the Signhost server. The system is preparing your document(s) for signing or processing the signature(s) placed on your document(s).
How long does this status last?
Typically, processing a request takes 1 to 30 seconds. The exact duration can vary depending on server load and the size of the documents you've submitted.
What if the status remains stuck for too long?
If the status is still 'In progress' after 5 minutes, there's likely an issue with the transaction. The cause is often related to the documents you've sent. Please check if your documents meet our PDF requirements and pay extra attention to the following points:
File type and security: Is it a supported PDF file without built-in logic or security? PDFs secured with a password or digital certificate cannot be edited and are therefore not supported.
Signer tags/signature fields: Are all signer tags or signature fields correctly placed? If you're using the API, do the custom signer tags match the tags in the document?
Fillable fields: Has the document been made fillable according to our instructions (see instructions for making a PDF fillable with Adobe here)? For example, do all fillable fields have a unique name and are they linked to a signature field?
Tip: If the document does not contain fillable fields and only needs to be signed, try printing it to PDF (see how to do that here). This removes invisible elements in the document that can cause problems. This simple step often resolves the issue.
Important to know
If a transaction remains in the 'In progress' status (status 20) for longer than 5 minutes, it's likely that this transaction will not succeed. In such a case, you can cancel the transaction, consult the information above, and create a new transaction after making adjustments.
As long as a transaction has the 'In progress' status, the documents are not available for download or for viewing the signatures. You can only view and download the signed documents once a transaction has reached the 'Signed' status (status 30).
Our support team is happy to assist you via chat or via support@signhost.com