Timeout limits in your NetSuite Connector can be configured to control how long a process should wait before timing out (and not waiting indefinitely). This helps to identify NetSuite processes that may not have completed, especially when no timeout response has been received from NetSuite.
This can be done mainly through two optional Business Process parameters: request.timeout and connection.timeout.
- The request.timeout parameter causes a Business Process to fail and throw a Read timed out exception in the Auditor logs when a given Business Process (request) takes more time to give the response than the specified time (seconds) as set in the parameter.
- The connection.timeout parameter causes a Business Process to fail and throw a connect timed out exception in the Auditor logs when a given Business Process (request) takes more time to connect to NetSuite than the specified time (seconds) as set 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 should the given BP request not be received within 5 seconds of the request.
Should the task fail, a Read timed out log entry would appear in the Studio's Auditor log.
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 should the given BP request not be received within 10 seconds of the request.
Should the task fail, a connect timed out log entry would appear in the Studio's Auditor log.
Comments
0 comments
Please sign in to leave a comment.