Make: ModuleTimeoutError: The operation timed out
Last verified
ModuleTimeoutError - The Operation timed outWhat it means
Make raises ModuleTimeoutError when a request sent by a module does not receive a response within the expected timeframe. Make's documentation says modules wait up to 40 seconds, with most modules having a 40 or 60 second limit. In scenario history it usually appears as "The operation timed out".
It typically happens when the external server is slow because of temporary service issues or overload, or when a single request asks for too much: a large search, a big file, or an AI model generating a long response. Make Community threads report it most often on email watchers, SFTP, SQL and AI API modules.
What is not wrong: your credentials and usually your mapping. The service did not answer in time.
What it looks like
ModuleTimeoutError - The Operation timed out
Retry handler: 3 attempts, interval 5 minWhy it happens
- The external service is slow or overloaded.
- A search module requests too many records at once.
- Long-running operations (AI generation, large file transfers) exceed the module's limit.
- A self-hosted server or database is slow to accept connections.
How to fix it
- Add a Retry error handler to the module, and enable Store incomplete executions so timed-out runs are not lost.
- Lower the Limit setting on search and list modules, as Make suggests.
- Use the API's asynchronous pattern where offered: start the job, then poll for the result in a later step.
- For your own custom app, raise the timeout in the Developer Hub if the API is legitimately slow.
- Check the service's status page and performance at the time of the error.
How to stop it recurring
Keep each operation small, prefer asynchronous APIs for slow work, and attach Retry handlers to modules that call slow services. Long scenarios can also hit ExecutionInterruptedError.
Official documentation: help.make.com/fix-errors-and-warnings. See all Make error messages or the Make limits and quotas.
Related errors
Definitions
- Make (formerly Integromat)Make (formerly Integromat) is a visual automation platform that connects apps and designs complex workflows us
- Error HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, inc
- Rate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given
- Retry LogicRetry logic is a fault-tolerance pattern that automatically re-attempts failed operations with configurable de
Quick answers
What does "ModuleTimeoutError: The operation timed out" mean in Make?
Make raises ModuleTimeoutError when a request sent by a module does not receive a response within the expected timeframe. Make's documentation says modules wait up to 40 seconds, with most modules having a 40 or 60 second limit. In scenario history it usually appears as "The operation timed out".
How do I fix "ModuleTimeoutError: The operation timed out"?
1. Add a Retry error handler to the module, and enable Store incomplete executions so timed-out runs are not lost. 2. Lower the Limit setting on search and list modules, as Make suggests. 3. Use the API's asynchronous pattern where offered: start the job, then poll for the result in a later step. 4. For your own custom app, raise the timeout in the Developer Hub if the API is legitimately slow. 5. Check the service's status page and performance at the time of the error.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.