Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property limits the indirect triggering of flows and subflows to a specified integer value, enhancing transaction stability. |
| What area does it affect? |
Flow Engine |
| What does the default mean? |
The default value is "3", which sets the baseline numeric behavior for this property. |
| When should you review it? |
Review this property when optimizing flow performance or troubleshooting transaction issues. |
Out of the box property record
Raw metadata from the property record.
| Property name |
com.glide.hub.flow_engine.indirect_recursion_limit |
| Sys ID |
39d80e3f13000300139e39ed9344b087 |
| Type |
integer |
| Application |
Global |
| Default value |
3 |
| Description |
Number of times that a flow or subflow can be indirectly triggered during a transaction. |
| Updated |
2024-05-25 04:32:56 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... • Does not exist within the specified application scope, or the flow or scope name has been misspelled. • Is not activated. • Exceeds the recursion limit set by the com.glide.hub.flow_engine.indirect_recursion_limit system property. The default value is three. //Example 1: Run a flow with a record-based trigger (function startFlowAsync() { try { © 2026 ServiceNow, Inc. All rights reserved. ServiceNow, the ...
Context preview
Snippet 2
... By default, the system stops triggering flow runs after the run count reaches the indirect recursion limit of three runs. Administrators can change the limit by setting the system property com.glide.hub.flow_engine.indirect_recursion_limit to an integer value equal to or greater than one. The system ignores any property value less than one and instead uses a limit of one. Consider the performance impact ...
Related properties