A request reaches
the right person.
See a clear rule, a repeated request, and a decision that needs a person.
Fictional local example. Recorded October 28, 2026. The controls replay saved results. Email, document processing, and customer systems are not connected.
Recorded step 1 of 6
Route a request
A fictional request matches a configured rule. The local example assigns Operations and saves one local task.
A clear rule gives the request a visible owner.
Request state at this step
| Request | Owner | State | Revision |
|---|---|---|---|
| REQ-101 | Operations | routed | 1 |
See the local tasks
- REQ-101 Operations · approved revision 1
Recorded outcome: routed. This panel replays saved evidence. It does not execute a workflow.
Recorded step 2 of 6
Recognize a repeat
The same request identity and content arrive again. The saved result stays in place. The local task count remains one.
A repeat should not become extra work for the team.
Request state at this step
| Request | Owner | State | Revision |
|---|---|---|---|
| REQ-101 | Operations | routed | 1 |
See the local tasks
- REQ-101 Operations · approved revision 1
Recorded outcome: duplicate. This panel replays saved evidence. It does not execute a workflow.
Recorded step 3 of 6
Hold an unknown
The category has no configured route. The request stays visible for a person. No extra task is created at this step.
Uncertain routing needs a person, rather than a guessed destination.
Request state at this step
| Request | Owner | State | Revision |
|---|---|---|---|
| REQ-101 | Operations | routed | 1 |
| REQ-102 | Needs a person | held | 1 |
See the local tasks
- REQ-101 Operations · approved revision 1
Recorded outcome: held. This panel replays saved evidence. It does not execute a workflow.
Recorded step 4 of 6
Reject an old approval
A person has assigned Support, which creates revision 2. An approval for revision 1 is rejected. Reviewer labels here are test metadata, not authenticated accounts.
A decision needs to match the version that was reviewed.
Request state at this step
| Request | Owner | State | Revision |
|---|---|---|---|
| REQ-101 | Operations | routed | 1 |
| REQ-102 | Support | held | 2 |
See the local tasks
- REQ-101 Operations · approved revision 1
Recorded outcome: stale_review_rejected. This panel replays saved evidence. It does not execute a workflow.
Recorded step 5 of 6
Approve the current version
The approval refers to the current revision. The local example creates the second task for Support.
Review can unblock the specific request that needs attention.
Request state at this step
| Request | Owner | State | Revision |
|---|---|---|---|
| REQ-101 | Operations | routed | 1 |
| REQ-102 | Support | routed | 2 |
See the local tasks
- REQ-101 Operations · approved revision 1
- REQ-102 Support · approved revision 2
Recorded outcome: approved. This panel replays saved evidence. It does not execute a workflow.
Recorded step 6 of 6
Recover after a restart
The example deliberately loses the acknowledgement after saving REQ-103, then reopens the local database. A retry finds the saved result. Three requests still have three local tasks.
A retry needs evidence about work that already happened.
Request state at this step
| Request | Owner | State | Revision |
|---|---|---|---|
| REQ-101 | Operations | routed | 1 |
| REQ-102 | Support | routed | 2 |
| REQ-103 | Operations | routed | 1 |
See the local tasks
- REQ-101 Operations · approved revision 1
- REQ-102 Support · approved revision 2
- REQ-103 Operations · approved revision 1
Recorded outcome: duplicate. This panel replays saved evidence. It does not execute a workflow.
What this example shows
Request routing, repeated-request handling, approval of the current revision, and recovery inside one local database. The local code passed 14 tests on October 28. These are local checks, without a claimed client result or measured saving.
A connected build needs its own permissions, input validation, provider checks, and acceptance review. A saved local task does not guarantee delivery to another service.
Read the duplicate-action guide ↗Start with
one handoff.
Bring the trigger, tools, and a redacted example. We can agree a useful first step.
Discuss your workflow ↗