Workflow Studio flow system properties
- UpdatedJun 2, 2025
- 11 minutes to read
- Yokohama
- Create Workflows
Configure how the system processes flows.
These properties are available for Workflow Studio.
To set Workflow Studio system properties, select Process Automation > Properties or navigate to the System Properties [sys_properties] table.
| Property | Description |
|---|---|
| The maximum number of records to return when fetching
data sn_flow_designer.action_picker_limit |
Specify the maximum number of records a look up action or step can return.
Workflow Studio ignores
records that exceed this limit.
|
| Set to True to show duration in the stage
column com.glide.hub.flow_engine.stage_display.show_duration |
Specify whether flows with stages display a duration.
|
| Allow the option for select users to write a script to populate the value of
an input on Flow and Action
Designers. sn_flow_designer.input_scripts_enabled |
Control permission to write inline scripts to compute input values.
|
| Specify the log level of system log entries to replicate to the flow log. The
system only replicates log entries of the specified level or
higher. com.glide.hub.flow_engine.listener_trace.threshold |
Specify the threshold required for Workflow Studio to replicate a system log entry to the flow log. These messages are generated by the ServiceNow AI Platform in response to flow execution outputs. For example, a message generated by a business rule that was triggered by a flow record operation. The system only replicates log entries of the
specified level or higher. Choices include:
|
| com.glide.hub.flow_engine.log_level | Specify the level of messages generated by the Flow Designer execution engine to write to the sys_flow_log table. These messages are generated when the flow engine runs the actions and flow logic of a flow.
For example, a message generated by running the Create record action. The system only writes log entries of the specified level or higher. Choices include:
The log level determines what if any log messages are added to the sys_flow_log table.
|
| The maximum number of iterations that a loop will run in Workflow Studio. sn_flow_designer.max_iterations |
Specify the maximum number of times that a loop can run before being stopped. A loop stops running when it iterates beyond this value, preventing infinite loops. This property only applies to Do the following
until and Go back to flow logic.
Note: Changing this value doesn’t apply to flows that are already running. |
| Enable flow engine debug messages in the system
log com.glide.hub.flow_engine.debug |
Enable or disable logging Workflow Studio debug messages
in the system log. All debug messages start with a Flow
Designer: string prefix.
|
| Number of times that a flow or subflow can be indirectly triggered during a
transaction com.glide.hub.flow_engine.indirect_recursion_limit |
Specify the maximum number of times a flow or subflow permits indirect
recursion. Workflow Studio
ignores all further calls or trigger condition matches from indirect recursion
after the limit has been reached. Set the value to any integer equal to or greater
than one. The system ignores any property value less than one and instead uses a
limit of one. Set the value to one to prevent all indirect recursion.
|
| The maximum number of actions allowed on a
flow. sn_flow_designer.max_actions |
Specify the maximum number of actions a flow or subflow can contain. Workflow Studio prevents you
from adding further actions after the maximum number of actions has been reached.
Consider the performance impact raising the maximum number of actions may have.
For example, running more actions may conflict with the default transaction quota
rule that prevents flows from running longer than an hour.
|
| The maximum number of allowed steps on an action. sn_flow_designer.max_action_steps |
Specify the maximum number of steps that an action can contain. Workflow Studio prevents you from adding further steps after the
maximum number of steps has been reached. Consider the performance impact raising
the maximum number of steps may have. For example, running more steps may conflict
with the default transaction quota rule that prevents flows from running longer
than an hour.
|
| Level of reporting data generated by the flow
engine. com.snc.process_flow.reporting.level |
Specify when Workflow Studio generates execution details and what information the details include. Options include:
The reporting level determines what if any flow execution details are generated. If a flow runs while reporting is off, execution details are never available for the flow, even if the reporting level later
changes. If a flow runs while reporting is activated, execution details are always available for that flow execution, even if the reporting level later changes.
|
Number of recent iterations to report for Do until and For Each loops. com.snc.process_flow.reporting.iteration.lastn |
As of the Xanadu release, this property has been removed and can no longer specify the number of recent iterations to report in the flow execution details. By default, all flow loops only store execution
details for the first and last iterations of a loop. To report on all iterations of a loop, create a flow execution setting record for each flow that you want to collect loop execution details. For more
information about flow execution settings, see Flow execution settings.
|
Truncate runtime values in the flow execution details step configuration com.snc.process_flow.reporting.serialized.val_size_limit |
Specify the number of bytes the system has to write runtime values to the flow execution details. To prevent truncation of runtime values, set the value to an integer equal to or less than zero. Preventing
truncation of runtime values requires additional system resources and may impact system performance.
|
Maximum inputs per action sn_flow_designer.max_action_vars |
Specify the maximum number of inputs that can be added to an action. Workflow Studio prevents you
from adding further inputs after the maximum number of inputs has been reached.
Consider the performance impact raising the maximum number of action inputs may
have. For example, processing more action inputs may risk the action running for
more than an hour and being stopped by the default transaction quota rule.
|
Maximum script variables per Script step sn_flow_designer.max_script_variables |
Specify the maximum number of input and output variables that can be added to
a Script step. Workflow Studio
prevents you from adding further script variables after the maximum number of
variables has been reached. Consider the performance impact raising the maximum
number of script variables may have. For example, processing more script variables
may risk the Script step running for more than an hour and being stopped by the
default transaction quota rule.
|
Maximum number of branches allowed for the Make a decision flow logic sn_flow_designer.max_decision_branches |
Specify the maximum number of branches to use when the Use
Branches option is selected for the Make a
decision flow logic.
|
Option to enable users to create flow variables. sn_flow_designer.flow_variables_enabled |
Specify whether users can create custom variables for their flow.
|
Maximum number of popular actions sn_flow_designer.action_picker.popular_actions.max_number |
Specify the maximum number of popular actions to display in the Action
picker.
|
Number of consecutive days used to generate popular actions sn_flow_designer.action_picker.popular_actions.last_num_of_days |
Specify the number of consecutive days used to generate popular actions. For
example, the default value of 7 generates popular actions based on action usage
during the last week.
|
com.glide.hub.flow.restricted_caller_access.track_flows_as_source |
Allow the system to generate restricted caller access privilege requests for flows and actions. The access privileges for flows and actions supersede any existing access privileges for script includes and
business rules that call flows and actions. This property is inactive on instances upgraded from San Diego and earlier releases. Customers who want to continue using script-based access privileges for flows and actions shouldn’t enable this property. Enabling this property requires you to
regenerate and approve access privileges for your flows and actions.
|
com.glide.cs.fdih.interactive.timeout |
Specify the length of time, in seconds, before the Workflow Studio
Integration Hub action workflow times out.
|
com.glide.hub.pause_low_priority_flows_enabled |
Enable or disable the pausing of low-priority flows when there are
high-priority flows waiting to run.
|
com.glide.hub.flow_engine.stage_display.show_approvers |
Show or hide the list of approvers assigned to a stage from a stage field. Set the value to true to show the list of approvers assigned to a stage. Set the value to false to hide the list of approvers
assigned to a stage.
|
| com.glide.hub.flow_engine.stage_display.show_approvers_limit | Specify the maximum number of approvers to display in a stage field as an integer value. Setting this value above 10 risks causing rendering errors in a list view. The stage field for one record can become so
big that the list cannot display additional records in the list.
|
| com.glide.hub.flow.current_stage_status_on_cancel | Specify the status to apply to the currently running stage when the flow is cancelled. Options include:
Any remaining stages after the current stage are set to the cancelled status. For example, suppose that a flow has three stages, and that the flow is currently running the first stage. Cancelling the flow sets that status of stage one to complete. Stages two and three are set to the cancelled status.
|
| com.glide.hub.flow.approval.allow_inactive_entity |
Specify which types of inactive entities to create approval records for. Options include:
Use the INDIVIDUAL option to create user approval records for inactive users who are not members of a group. This option doesn't create group approval records for inactive groups, nor does it create user approval records for group members. Use the GROUP option to create a group approval records for inactive groups. This option also creates individual user approval records for group members who have active user records. This option doesn't create individual user approval records for group members who have inactive user records. Use the INDIVIDUAL,GROUP option to create user approval records for inactive users and group approval records for inactive groups. This option also creates individual user approval records for group members who have active user records. Inactive group members don't receive user approval records. Use a null or empty value to prevent creating group approval records for inactive groups, and also prevent creating user approval records for inactive users.
|
| com.glide.hub.flow_api.default_execution_time | Specify the default duration in milliseconds your Flow API calls can run. Use this property to give Flow API calls in spokes more time to run. The maximum value of this property is limited by REST transaction
quotas, which by default the system stops after 60 seconds.
|
| com.glide.hub.flow.approval.show_approver_name_in_audit | When true, the audit history generates a comment containing the name of the person who made an approval and the change made in the approval field. For example, an approval message might read,
"Fred Luddy | Approval | Approved was Requested." When false, the audit history shows the name of the person who started the flow that ran the Ask for the approval action.
|
| com.glide.hub.flow.approval.show_higher_role_audit_comment | When true, the audit history generates a comment containing the name of the person who made an approval and a note that the approval permission was granted by a role. For example, an approval message might
read, "Fred Luddy approved, permission granted by role." A rejection message might read, "Fred Luddy rejected, permission granted by role." When false, no
comment is generated.
|
| com.glide.hub.flow.approval.show_delegate_audit_comment | When true, the audit history generates a comment containing the name of the person who made an approval and a note that the approval was made while acting as a delegate of another user. For example, an
approval message might read, "Abraham Lincoln approved the task as delegate of Fred Luddy." A rejection message might read, "Abraham Lincoln rejected the task as delegate
of Fred Luddy." When false, no comment is generated.
|
| com.glide.hub.flow.approval.show_impersonate_audit_comment | When true, the audit history generates a comment containing the name of the person who made an approval and a note that the approval was made while impersonating another user. For example, an approval message
might read, "System Administrator approved the task by impersonating Fred Luddy." A rejection message might read, "System Administrator rejected the task by impersonating
Fred Luddy."
|