Definition
Deadline propagation passes the time remaining for a request to downstream operations instead of giving each operation a fresh full timeout. It coordinates a workflow-wide waiting limit across inventory, delivery, and other dependencies. Deadline expiry ends the permitted wait; it does not prove an external write was rolled back.
Why It Matters
- A chain of individually acceptable service waits can exceed the time available for the whole customer interaction.
- Within a Commerce Intelligence OS, a bounded decision needs an explicit unresolved outcome when required evidence cannot be obtained before the workflow deadline.
How It Works
- Set an overall request budget based on the interaction and service behavior. Account for network, processing, and response handling time rather than allocating the whole budget repeatedly.
- Before each downstream call, derive a remaining budget and pass it using the supported protocol. Inspect framework behavior because propagation and defaults vary by implementation.
- Make handlers observe cancellation and stop unnecessary dependent work. Do not assume that client cancellation automatically stops every server-side task.
- Separate timeout from business completion. For an ambiguous write, retain operation identity and reconcile against the authoritative system before retrying or reporting failure.
Ecommerce Example
Context: Illustrative example: an assistant has a three-second interaction budget. Inventory checking and orchestration consume 1.2 seconds.
Recommended move: The delivery step has at most 1.8 seconds remaining, with some of that reserved for returning a response. It must not start another full three-second wait.
Why it matters: If delivery confirmation remains unavailable, the assistant reports it as pending. This example illustrates budget accounting, not a measured iKawn latency target.
iKawn Framework
Budget
The iKawn framework defines the time available for a commercial decision.
Propagate
Carry remaining time across dependent checks.
Cancel
Stop work that can no longer serve the active request where supported.
Reconcile
Keep uncertain external effects visible until completion is confirmed.
Concise Summary
Propagate one remaining time budget across the workflow. Treat deadline expiry, cancellation, and confirmed business completion as separate states.