What does a request timeout or operation timed out error mean?
A timeout occurs when an operation does not produce the expected response within an allowed period.
Timeouts can affect browser requests, AI processing, external integrations, workflow steps, or other operations that depend on communication between services.
A timeout does not always mean that the underlying operation failed completely.
Why do timeouts happen?
Possible causes include:
1. Temporary network interruptions.
2. Slow responses from external services.
3. Complex AI processing.
4. Delays in a connected API.
5. Temporary service congestion.
6. Unavailable dependencies.
7. An operation exceeding an applicable processing limit.
What should I do first?
1. Record the affected operation.
2. Check whether the operation has an execution record.
3. Review its current status and available technical details.
4. Determine whether an external integration was involved.
5. Check whether the expected result already exists.
For example, if a request timed out while creating a CRM record, verify the CRM before submitting the same request again.
Can a timed-out operation still complete?
Depending on where the timeout occurred, it is possible for a request to lose its response even though an underlying action has already been performed.
This is particularly important for operations with external side effects.
Should I retry?
Retry only after determining whether the original operation completed or produced partial results.
If the operation is read-only, a retry may present less risk than repeating an action that modifies business data.
What if timeouts occur repeatedly?
Check whether the problem affects a specific integration, AI Employee, workflow, or type of request.
A recurring timeout affecting one dependency may indicate a different problem from timeouts affecting the entire platform.
When to contact Support
Include the operation name, approximate start time, timeout message, relevant execution identifier, and whether the action produced any visible results.
Do not repeatedly trigger high-impact operations while their execution state remains uncertain.