system property glide.hub.process.sync.jobs.inbound.subflow.execution_time

[Nagasri]

currently the value of the system property "glide.hub.process.sync.jobs.inbound.subflow.execution_time" is 30000, but we want to increase to 60000. Will there be any issue here. Please help

[Dr Atul G- LNG]

Hi @Nagasri 

You can increase the limit, but it is not recommended as it may impact system performance. Increase the limit only if it is truly required and after careful evaluation.

https://www.servicenow.com/community/developer-forum/flowapi-times-out-in-30-secs/m-p/1806516

https://developer.servicenow.com/dev.do#!/reference/api/zurich/server/sn_fd-namespace/ScriptableFlow...

[vaishali231]

hey @Nagasri 

Yes — increasing the system property glide.hub.process.sync.jobs.inbound.subflow.execution_time from 30000 (30 seconds) to 60000 (60 seconds) is generally safe.

This property mainly controls how long the platform will wait for an inbound synchronous subflow to complete before timing out. So increasing it just allows the subflow to run longer before it fails due to timeout.

That said, a couple of things to keep in mind:

1. If you have high-volume inbound integrations, longer wait time can keep worker threads busy for a longer period.
2. It may also cause the calling system to wait longer for a response.
3. If the subflow consistently takes more than 30 seconds, it’s worth reviewing the subflow steps (scripts, lookups, API calls, etc.) to see if performance can be improved.                                                                              

 In most normal cases, moving it to 60000 does not cause issues and is a common adjustment when inbound subflows are timing out.

************************************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.

Regards
Vaishali Singh