Short answer
Why Is My API Request Timing Out?
An API request times out when the server responds too slowly, the request transfers too much data, network resolution fails, or synchronous processing exceeds the automation platform limit. Measure where the delay occurs, request less data, move long work to an asynchronous job, and retry only safe idempotent requests.
Common causes
- The endpoint performs expensive work before responding.
- The response or uploaded file is too large for the platform timeout.
- DNS, TLS, proxy, or regional network problems delay connection setup.
- The API is degraded, rate limited, or waiting on another dependency.
Diagnostic steps
- Record the endpoint, method, payload size, timestamps, and platform timeout message.
- Test a minimal request and check provider status and server logs where available.
- Use pagination, smaller files, or an asynchronous job endpoint for long-running work.
- Add bounded retries only for safe requests and verify whether the timed-out request already completed.
Example
A report-generation POST takes two minutes but the automation step allows less. Start the report job, store its job ID, and poll for completion later.
Caveats
A timeout does not prove failure; the server may finish after the client disconnects. Retrying a create request can produce duplicates.