Managing Timeout Limits

Timeout limits in your connector can be configured to control how long a process should wait before timing out (and not waiting indefinitely). This helps to identify connector processes that might not have completed, especially when no timeout response has been received from the server.

Connection and request timeout limits can be configured for the following connectors:

• Acumatica
• Adobe Commerce
• Amazon Marketplace (AMP) SP-API
• D365 Business Central - D365 BC
• D365 Supply Chain Management - D365 SCM
• eBay
• SAP S/4 HANA
• Shopify

The request.timeout and connection.timeout parameters cause a Business Process to fail and throw a Connection timeout exception in the Auditor logs when a given Business Process (request) takes more time to respond than the time specified (seconds) in the parameter.

Both are optional and independent of each other. They can be used together or separately.

Examples

Here is an example of the request.timeout parameter being used in a Set Value Business Process task. For this particular case, the task has been set to fail and throw an error if the given HTTP call is not processed within 5 seconds of the request.

Here is a similar example of the connection.timeout parameter being used in a Set Value Business Process task. For this particular case, the task has been set to fail and throw an error if the connection is not established with the server within 5 seconds of the request.