Timeouts

Connection idle timeout

Every connection the automator opens to an external system is subject to a 5-minute idle timeout. When no data is sent or received over the connection for 5 minutes, the automator closes it and the function fails with a timeout error.

Note that this is an idle timeout, not a limit on the total duration of a request. In other words, a connection that keeps transferring data never times out, however long it runs. Streaming a large file that takes more than 5 minutes to download is fine, as long as data keeps arriving. The timeout only fires when the connection stays silent for 5 minutes; for example when a server needs a long time minutes to start responding, or pauses mid-response.

It applies to all external connections, including the HTTP, REST, SOAP, Xurrent REST API and Xurrent GraphQL API functions, the proxy functions, and the file-streaming functions stream_to_file, stream_to_uri and stream_to_archive.

To avoid idle timeouts, it is usually recommended to fetch large amounts of data in smaller batches, for example through a paging API. This prevents the connection from sitting idle while the server assembles a large response.

Maximum execution time

A package execution may run for at most 4 hours. Integrations that need more time than this should split the work over multiple executions. An execution that exceeds this limit is aborted and marked as failed. If the package has one configured, an error notification mail will be sent.

When a package is in the middle of a long-running operation, the automator will attempt to abort that as well. For example, when a HTTP call to an external system is ongoing, the connection will be closed.