Sometimes, you may be surprised to find that your workflow abruptly falls into a suspended state. You may not see any indicators or explanation as to why. This article will help explain some possible causes.
There are a few possible causes for suspended workflows:
1. The signer may have uploaded a file that's not a supported format: Sometimes, the signer uploads a ZIP archives instead of one of the supported file formats. This can be found by examining the workflow instance endpoint and downloading all of the files sent to it.
2. The signer may be trying to run a task in a private window or an incognito window: When this happens, the user's identity becomes anonymous, which throws things off. When examining the workflow instance, you may notice "anonymous" as a user name, which shouldn't happen.
3. There may be a reference to a property value that no longer exists in the workflow: When creating the workflow someone may have designed their workflow so that a property unexpectedly changes its value prior to a task needing it. The result is a task getting a bad value for the property, leading to a suspended workflow.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article