Stockertim Dictionary · Technology · Artificial intelligence
Timeout
Also called time-out, timeouts, request timeout
In short
A timeout is the longest time a workflow waits for a step or an outside system to answer before treating the attempt as failed and following its retry or error path.
- Beginner
- Concept
- Checked
In detail
When a workflow calls another system, the reply usually comes in seconds. Sometimes it does not: the system is overloaded, the network drops the request or a model is generating a very long answer. Without a limit, the workflow would wait indefinitely, holding up the item and often the items behind it. A timeout sets that limit. When it passes, the attempt is abandoned and treated as a failure.
Choosing the value needs measurement. It should sit comfortably above the normal response time, so that ordinary slow replies are not cut off, but well below the point where waiting causes harm. A data lookup that normally answers in one second might get ten; a model call producing a long document might need a minute or more. Web services signal timeouts in standard ways, for example the HTTP status codes 408 Request Timeout and 504 Gateway Timeout.
A timeout does not prove the action failed. The other system may have received the request and completed it after the caller stopped waiting. Retrying blindly can then create a second payment or a duplicate record, so actions with effects carry a unique reference that lets the receiving system recognise and ignore a repeat.
Timeouts also add up. Several retries, each waiting the full limit, can make one item take minutes, which matters when a person or another process is waiting for the result.
Worked example
A workflow at Elmstead Pharmacy checks stock with a wholesaler's system that normally answers within 2 seconds.
- Timeout set at 15 seconds, well above normal but short enough for staff waiting at the counter.
- Worst case with 3 attempts at the full limit: 3 x 15 = 45 seconds
- After the third timeout the request goes to the error path and staff are told to phone the wholesaler.
A slow wholesaler system delays staff by at most 45 seconds before they switch to the phone.
In practice
Builders set a timeout on every call to an outside system, base each value on measured response times, pair timeouts with limited retries and unique references for actions, and alert when timeouts become frequent.
Watch out
- A timed-out request may still have succeeded; retrying without a unique reference can duplicate it.
- No timeout at all lets one stuck call block a whole queue.
Learn it properly
Official sources
- RFC 9110: HTTP Semantics · Internet Engineering Task Force
- Monitoring the status of your service · Government Digital Service
Facts last checked on 9 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.