Request is stuck or a signer is missing

A request can be submitted while one or more signing steps remain. Locate the current task before sending another invitation or changing the form. The response's board column alone may not describe every signer's state.

Find the unfinished step

Open the response or signed-record activity. Read each relevant role and state: Request sent, Not signed, Signed, or Signature not required for a skipped optional role. Match the signer and their assigned email to this response.

For sequential signing, check the preceding required signer. For parallel signing, check all required signers in the active stage. An internal approval action can also be a separate step from the respondent's initial signature.

Inspect recipient and rule configuration

1. Confirm the expected role exists in the workflow.
2. Check whether the recipient is fixed or read from an answer.
3. Inspect that answer on the affected response; a missing email can prevent the expected invitation.
4. Review conditional criteria using the submitted values, not only the current form defaults.
5. Check whether an optional role was deliberately skipped for that response.

An optional role that is correctly skipped should not be treated as an unsigned required signer. Do not add a dummy signature to make a request appear complete.

Check follow-up configuration

A reminder depends on the configured active step, recipient and timing. It is not proof that the request is overdue merely because no reminder has arrived. Review schedules and reminders and any paused schedule.

In current workflows, signed-PDF generation waits for required signatures. Automatic movement to a completed board status is another setting. A finished signing process can therefore need an owner-defined staff action even when its signatures are complete.

Resolve without losing context

Use the supported response/task actions for follow-up and verify the result. Before editing a live workflow, consider other requests still using it. A new role or default recipient does not automatically explain how existing requests will be affected.

After correction, confirm the right person can open their task, complete it, and advance the process. Keep the original response and activity when investigating an error. If the expected state remains unclear, give support the role, stage, visible state and error, using synthetic or redacted details.