Completed fictional example: Build a manual exception queue into your automation

All people, identifiers, amounts, outcomes, and evidence are fictional. This demonstrates a completed record, not a client project or account trial.

Exception ID / source event / arrival / execution

E-014 / form-demo:evt-014 / October 2, 10:00 America/New_York / run-demo-08

Reason and stop type

Two possible people; human identity decision

Source reference and access check

Demo source S-014 opened by Morgan and Casey

Effects already performed at the destination

No job created; destination register checked by source ID

Owner / backup / review date

Morgan / Casey / October 2 by 3 p.m.

Available choices and exact effect of continuing

Link C-014 or C-015, or ask for information; continuing creates a job and sends no message

Decision / reason / evidence / person / time

C-014; client confirms company in demo message S-015; Morgan at 2 p.m.

Resulting ID and destination check

J-014; original source and contact C-014 found after creation

State / next action / closure or new failure

Closed after readback in the fictional case; no real systems were changed

Three alternative branches

• S-014 is inaccessible: state awaiting access; Morgan repairs permissions by an agreed date. Do not infer identity or permission to continue.
• J-014 already exists but its backlink is missing: find it using form-demo:evt-014, verify the contact and content, then repair the reference. Do not create another job. Keep an ambiguous match pending.
• The same evt-014 arrives again: update E-014 while retaining its decision and J-014. A new evt-015 from the same client is separate; email is not an event ID.

These branches do not claim execution in an account. Record the actual owner, date and read-back destination in the real queue.