For the complete documentation index, see llms.txt. This page is also available as Markdown.

🛠️Exception Resolution

Exception Resolution

Exception Resolution is the screen for visible failures. Use it when a workflow cannot finish because something is missing, blocked, or failed.

Exception Resolution screen type in the builder.

Exception Resolution screen type in the builder.

What belongs here

Common exceptions include:

  • Missing reviewer

  • Missing required field

  • Recipient has no access

  • Destination screen missing

  • Message failed

  • Webhook failed

  • Linked app unavailable

  • Decision action not mapped

  • Repair needed after a template or demo was provisioned

Setup steps

  1. Add Exception Resolution.

  2. Connect workflows to the exception destination.

  3. Decide which maker, admin, or operator roles can see it.

  4. Show the failed record, workflow, failure reason, and suggested fix.

  5. Add retry or repair actions when available.

  6. Test one failure path deliberately, such as missing reviewer.

  7. Confirm the exception appears with useful language.

Verification

Exception Resolution is ready when a maker can diagnose the failure from the screen itself and knows the next action without opening backend records.