Interactive logic replay
Priority Incident Router
A condition recognizes an urgent checkout incident and sends only the matching branch into the fast lane.
3
executed nodes
3
recorded steps
2ms
actual runtime
2026-07-28
recorded on
Recorded run
Ready to replay · 2ms actual runtime
Replay the recorded run
Inputs are locked to the original execution so every replay stays honest and repeatable.
InboxLine
recorded inputUse the transport bar above to pause, seek, or change speed.
Real Heym run recorded on 2026-07-28. The replay is deterministic; node outputs and timings are the original execution data.
Inside the workflow
What happens in this run
A small workflow that demonstrates an important automation primitive: only the matching branch should execute. The recorded input describes a production checkout failure, the Condition node evaluates the URGENT marker, and the run continues through FastLane while the Standard output stays inactive. In a production workflow, those two outputs can become different escalation policies, notification channels, or response-time targets.
1InboxLinetextInput node · 0ms
Input
Output
from InboxLine
{
"headers": {
"content-type": "application/json",
"x-simple-response": "false",
"connection": "keep-alive",
"user-agent": "Bun/1.3.10",
"accept": "*/*",
"host": "localhost:10105",
"accept-encoding": "gzip, deflate, br, zstd",
"content-length": "94"
},
"query": {},
"body": {
"text": "URGENT: production checkout is failing for EU customers"
},
"text": "URGENT: production checkout is failing for EU customers"
}2IsUrgentcondition node · 2ms
Input
from InboxLine
{
"headers": {
"content-type": "application/json",
"x-simple-response": "false",
"connection": "keep-alive",
"user-agent": "Bun/1.3.10",
"accept": "*/*",
"host": "localhost:10105",
"accept-encoding": "gzip, deflate, br, zstd",
"content-length": "94"
},
"query": {},
"body": {
"text": "URGENT: production checkout is failing for EU customers"
},
"text": "URGENT: production checkout is failing for EU customers"
}Output
from IsUrgent
{
"branch": "true"
}3FastLaneoutput node · 0ms
Input
from IsUrgent
{
"branch": "true"
}Output
from FastLane
{
"result": {
"IsUrgent": {
"branch": "true"
},
"__heym_execution_context": {
"InboxLine": {
"headers": {
"content-type": "application/json",
"x-simple-response": "false",
"connection": "keep-alive",
"user-agent": "Bun/1.3.10",
"accept": "*/*",
"host": "localhost:10105",
"accept-encoding": "gzip, deflate, br, zstd",
"content-length": "94"
},
"query": {},
"body": {
"text": "URGENT: production checkout is failing for EU customers"
},
"text": "URGENT: production checkout is failing for EU customers"
},
"IsUrgent": {
"branch": "true"
}
}
}
}3 recorded steps · 2ms of real execution · recorded 2026-07-28
Put the pattern to work
Where teams use this pattern
- Separating urgent support incidents from the normal queue
- Routing high-risk transactions to manual review
- Sending priority events to a faster notification path
Start from the Urgent vs Standard Router template.
Browse more ready-made flows in the template gallery.
Run this workflow on your own Heym
Heym is Self Hosted and Source Available, clone it and spin up the canvas locally in under a minute, then run the workflow you just watched.