An assistant displays “failed” after a short wait, while the connected service continues processing. The user submits the request again and later receives two results.
Separate request time from operation state
AWS Step Functions’ error-handling guidance describes timeout, retry and catch mechanisms. Those technical controls still need to map to a comprehensible business status.
Use states such as submitted, processing, confirmed and unresolved where they fit. A timeout can change what the application knows without changing what the external service has done.
An illustrative AI report generator may continue working after the browser session ends. The interface should offer a way to retrieve the original task rather than encourage another submission.
Give the user an appropriate next action
Explain whether they should wait, check status or contact support. Do not instruct them to retry a consequential action before the system can establish its state.
Retain a stable task identifier and show it where useful. Support should be able to locate the task without asking the user to reconstruct the entire conversation.
If the system cannot verify completion, say so. A plausible generated explanation is not a transaction confirmation.
Reconcile late responses
Define how delayed results update the task and inform the user. Handle cancellation and expiry deliberately so a late response cannot reactivate work that has been superseded.
Measure unresolved duration and repeated submissions. A fast interface can still create poor service if it hides long-running uncertainty.
Include a test where the external service succeeds just after the application stops waiting. The result should update the original task rather than trigger a second submission. This scenario can reveal whether the system’s apparent error handling protects the business action or only reports the state of the network call.
Truthful state is an important part of trustworthy automation. The system should report what is known about the action, not merely whether its most recent network request finished on time.
Published by the Global Apex Tech Editorial Desk. Partner involvement, when applicable, is disclosed above the headline. For editorial questions or source material, contact editor@globalapextech.org.