You may encounter a workflow exception when a document sent through the workflow does not meet any of the criteria defined within a step or across the workflow. In such cases, the document is directed to the catch-all user, triggering the exception.



If the exception occurs midway through the workflow, it’s likely due to the step’s setting being configured as “Catch” rather than “Skip to Next.” This tells the system to send unmatched documents directly to the catch-all, rather than continuing through the workflow.



Similarly, if a document passes through the entire workflow without matching any criteria, and the final step is set to “Catch,” the system will also send it to the catch-all user.
Common reasons a document may not match workflow criteria include:
  • The document type has not been accounted for, and no “All” option has been added as a step.
  • The legal entity, cost centre, resource, department or other specified posting criteria hasn’t been included in any step.
  • The document amount doesn’t match any step criteria (e.g. steps looking for values under or over a figure, but not the exact figure).
  • The workflow is set to evaluate header details only, but a step includes detail-level criteria, causing the document to skip that step.
  • An attachment is included but the workflow step does not require an attachment
These are just a few examples—exceptions can occur for other reasons too so it is important to review the criteria used in the the workflow rules and whether this is is specified to match the document or record submitted.