- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2020 12:54 PM
This is about the error "com.glide.sys.ExecutionTimeoutException: An execution timed out with timeout of 30000 MILLISECONDS". I have the property "glide.http.outbound.max_timeout.enabled" to False and the property "glide.http.outbound.max_timeout" to 600 secs. In addition I have the Transaction Quota property REST Batch API request timeout set to 300. The strange thing is when I execute a scheduled job (client script) to execute a Sub Flow, it fails with that timeout error. However when I run the Sub Flow by itself in the Designer I have no problems finishing the flow without an error. Is this related to a property other than the ones I have mentioned? I have checked both sys_properties and Sys_Rule_Quota and see no other REST API related property with the value set to 30 secs, Where is this coming from and how can I override it?
Thanks
Solved! Go to Solution.
- Labels:
-
Integrations
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2020 01:21 PM
Hi Jazz,
The property is:
com.glide.hub.flow_api.default_execution_time
Default it is set to 30 seconds. If you do not see it you can add it to the System properties. Please try adding it and setting a higher value if you prefer.
It is mentioned here:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2020 01:21 PM
Hi Jazz,
The property is:
com.glide.hub.flow_api.default_execution_time
Default it is set to 30 seconds. If you do not see it you can add it to the System properties. Please try adding it and setting a higher value if you prefer.
It is mentioned here:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2020 01:29 PM
You should not be increasing this value to avoid performance issues.
Your flow execution should not exceed more than 30 secs. You need to see your scheduled job which for any query optimization.
Regards,
Sachin