Power Automate · Cloud flows: timeout and throttling errors
OperationTimedOut
Short answer
OperationTimedOut in a Power Automate cloud flow: A long-running operation (webhook wait, approval, HTTP polling) exceeded the maximum wait time. The most likely fix is to set explicit timeouts, use relay pattern.
VerifiedLast verified
01Error text
OperationTimedOut02Likely causes
- HTTP webhook action waiting for a callback that never came
- Approval action without an expiration, hitting the 30-day flow run limit
- "Delay until" action set to a date beyond the 30-day run duration limit
- External service went down and never sent the expected response
03How to fix it
- Always set explicit timeouts on webhook and approval actions.
- For HTTP webhook actions, implement a timeout branch with Configure run after > has timed out.
- Break long waits into shorter segments using a loop with daily checks.
- For the 30-day run limit, redesign long-running processes to use a "relay" pattern: End the current run and start a new one with state passed via Dataverse or a file.
iNotes
Cloud flows have a maximum run duration of 30 days. For processes that take longer, split them into multiple flow runs with shared state.
04Official documentation
→Related errors
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs