Key Features

• Execution Setting Records: You can create multiple execution setting records ([sysflowexecutionsetting]) for different flows, subflows, or actions to tailor execution detail collection.
• Reporting and Logging Levels: Configure the level of execution detail and logging messages captured during flow runs, which helps in monitoring and troubleshooting.
• Report All Iterations Option: Choose whether to gather execution details for all iterations of a loop or only the first and last, balancing detail with resource consumption.
• Flow Priority: Set the priority for running background flows, although this option is hidden by default and can be enabled if needed.
• Inheritance of Settings: Actions or subflows invoked from a parent flow inherit the parent's execution settings.
• Access: Execution setting records are managed through the Flow administration module.

Best Practices and Guidelines

• Avoid Enabling on Production: To prevent performance degradation, activate and configure execution settings only on non-production instances used for testing.
• Test Thoroughly Before Deployment: Use debug-level execution details to verify flows, subflows, and actions generate the necessary data before moving to production.
• Manage Resource Consumption: Limit memory usage by avoiding the "report all iterations" option unless needed for detailed troubleshooting.
• Use for Troubleshooting Only: Enable detailed reporting and logging settings temporarily during troubleshooting, then disable or delete these records to maintain optimal performance.

Practical Implications for ServiceNow Customers

By using flow execution settings, you gain granular control over monitoring and troubleshooting specific flows without impacting overall system performance. This targeted approach helps optimize resource usage and ensures that you collect only relevant execution data. Following the recommended guidelines will help maintain your instance’s stability while effectively diagnosing and resolving flow-related issues.