Portal Community
Flow Studio

Deadlines and Escalation

Every HIL node can have an optional timeout. If the actor does not respond within the deadline, the engine takes a configurable action: escalate, auto-decide, or fail.

Timeout Duration (ISO 8601)

FormatMeaning
PT30M30 minutes
PT4H4 hours
P1D1 day (24 hours)
P3D3 days
P1W1 week
null / emptyNo timeout — task waits indefinitely

Timeout Behaviours

BehaviorWhat Happens
EscalateTask reassigned to escalationActorId; original actor's task cancelled; deadline resets
AutoApproveEngine injects a synthetic Approved response; execution continues on approved port
AutoRejectEngine injects a synthetic Rejected response; execution continues on rejected port
FailEngine throws TimeoutError; workflow fails; timeout port NOT used

Timeout Port

The timeout output port fires when Escalate times out a second time (double-timeout), or when you configure it as the primary timeout action. Connect this port to a fallback path:

[Approval Node]
  ├─ approved → [Process Next Step]
  ├─ rejected → [Send Rejection Notice]
  └─ timeout  → [Escalate to CEO Node]  → [CEO Approval Node]
                                               └─ timeout → [Auto-Reject End]
No timeout = no safety net: If you set no timeout, the workflow can remain suspended indefinitely. Always set a timeout on production HIL nodes unless indefinite suspension is a deliberate design choice (e.g., long-lived workflow patterns).
← HIL Task Inbox Next: Guide Map →