Unblock a Workflow Session
Learn how to recover a Workflow Session when it becomes blocked due to a Signature Request or Verification failure.
When does a Workflow Session become blocked?
A Workflow Session — and the affected Action Group — enters blocked status when at least one Action inside it meets any of the following conditions:
| Action type | Blocking statuses |
|---|---|
| Signature Request | rejected, declined, canceled, expired |
| Verification (Identity, bank account, etc.) | inconclusive, failed |
Unblock when a Signature Request is blocking
To unblock the Workflow Session:
- Delete the blocking Signature Request. Use the Delete a Signature Request endpoint.
- Create a new Signature Request, and link it back to the Workflow Session using the
workflow_session_idparameter.
What happens to the deleted Signature Request?
The deleted Signature Request remains visible in the Action Group, with status deleted. However, deleted actions are ignored when computing the status of the Action Group. As a result, the Action Group will automatically exit the blocked state.
Unblock when a Action is blocking
When a Verification ends in failed or inconclusive, you have 2 options to resume the Workflow Session:
- Retry all blocked Actions in a Workflow Session until they've reached the status
verified - Resolve the Action manually
Option #1 - Retry a blocked Action
blocked ActionAn Attempt is a retry of the same Action when it reached a final blocking status.
Each new Attempt:
- Belongs to the same Action
- Becomes the main Action
- Marks the previous one as a
previous_attempt
When a retry is allowed?
Only final statuses that block the Action Group are eligible for retry:
| Resource Type | Retryable Statuses |
|---|---|
| Verification | failed, inconclusive |
| Signature Request | rejected, canceled, declined, expired |
💡 You can still retry even after data has been anonymized (after 7 days).
Verified and Done Actions cannot be retried.
You can only retry Action of the same type:
- An Attempt must use the same
resource_typeas the original Action.- ✅ Company Verification → Company Verification
- ❌ Company Verification → Signature Request
- ❌ Bank Account Verification → Bank Account Lookup / Bank Account Connection
Practical Examples
-
Verification (ID document) →
failedYou may create a new Attempt with updated images and resubmitted fields. The new Attempt becomes the main Action, the prior Attempt becomes a
previous_attempt. -
Signature Request →
expiredYou may create a new Attempt with fresh deadlines (and, if needed, updated recipient details). The new Attempt is now the main Action.
What are the rule of the Attempt?
- You have up to 10 Attempts per Action.
- Each new Attempt requires to change inputs before triggering a new Attempt.
- A new Attempt counts like a new verification.
- Resolved action cannot be retried.
What is the status of the Action Group?
The status of the Action (Verification or Signature Request) is always the status of the latest Attempt.
- The new Attempt’s status overrides the previous one.
- The Action Group status is recalculated each time based on the latest Attempt.
Example:
| Attempt | Status | Impact |
|---|---|---|
| #1 | failed | Action Group blocked |
| #2 | inconclusive | Action Group still blocked |
| #3 | verified | Action Group unblocked (status recalculated) |
The status of previous Attempts is no longer used to determine the current Action Group status.
What is the behavior of previous attempts?
Prior Attempts are frozen as previous_attempt and unsynced from the original resource_id.
Example: If a Signature Request (now a previous_attempt) is later deleted, the Action Attempts list is not updated with that deletion. This preserves context and coherence within the Action.
Option #2 - When can you resolve a Verification Action manually?
You may use manual resolution only if you have done the verification externally. Typical cases include:
- Manual human review. Example: A team member directly checks the ID document and confirms it is valid.
- Verification done outside the Workflow Session. Example: You use Yousign Verify manually (outside the session) to complete the verification separately.
How to resolve the Verification Action?
Use the Resolve an Action endpoint to mark the Action as resolved.
The Action Group will then treat it as if it were verified or done, and the Workflow Session will continue.
Responsibility noteResolving a Verification tells the Workflow that you’ve checked it outside of Yousign’s system.
Yousign does not validate it — the Workflow simply continues based on your confirmation.
The underlying Verification resource itself will remainfailedorinconclusive, but the Workflow logic ignores that once the Action is marked as resolved.
Updated 4 days ago