How to Access Logs in ServiceNow Flow Designer
- kelly.ryu
- Mar 20
- 3 min read
Updated: Mar 29
ServiceNow Flow Designer is a powerful tool for building automated workflows on the Now Platform. To effectively troubleshoot and maintain these flows, it’s crucial to know how to access and interpret their logs. Log access in Flow Designer helps administrators and developers identify errors, understand flow execution paths, and ensure that processes are running as expected.
In this article, we will explore how to view Flow Designer logs and execution details in ServiceNow. We’ll cover the steps to find error logs via the Application Navigator, various methods to review flow execution details, understanding system log entries (including the System Log modules and the sys_flow_log table), adjusting logging levels for flows, and best practices for analyzing flow logs. By the end, you’ll have a clear understanding of how to retrieve and use Flow Designer logs for troubleshooting and optimization.
Accessing Flow Designer Error Logs via Application Navigator
When a flow encounters an error, the first place to check is the ServiceNow System Logs. ServiceNow provides dedicated modules for viewing system errors and other log messages. To access flow error logs:
Use the Application Navigator: In the main ServiceNow interface (left-hand navigation), type “System Log” in the filter navigator.
Open System Log > Errors: Click on System Log > Errors. This will display a list of recent error-level log entries across the platform.
Identify Flow Errors: Look for entries related to your flow, which may reference the flow name, flow context ID, or specific actions.
Drill Down if Needed: Click on an error entry to view details. If necessary, use flow execution details for further investigation.
By starting with the Errors log, ServiceNow users can immediately catch critical issues in flows, especially after deploying new or updated flows.
Viewing Flow Execution Details in Flow Designer
Beyond the error logs, Flow Designer offers several ways to view flow execution details, including:
Test Execution Link: After testing a flow, click "Your test has finished running. View the flow execution details." to access execution details.
Executions List on a Flow: Open a flow in Flow Designer and click the Executions button to see historical runs.
Flow Designer Landing Page – Operations Tab: Navigate to the Flows tab within Operations to see system-wide flow runs.
Today’s Executions Module: Found under Flow Administration > Today’s Executions, listing all flows executed within the last 24 hours.
Active Flows Module: Access Flow Administration > Active Flows to review flows currently in progress.
Each of these methods provides a window into the flow’s operation, allowing developers to track the success or failure of workflows in detail.
Using ServiceNow System Logs for Flow Information
In addition to Flow Designer’s execution logs, the System Logs in ServiceNow can provide deeper insights into flow activity:
System Log > All: Displays all log entries, including informational messages and warnings.
Flow Designer Log Table (sys_flow_log): A dedicated table capturing flow-related logs.
System Log > Errors (Revisited): Critical flow errors will also be recorded here.
By combining Flow Designer execution details with System Logs, users gain a comprehensive view of flow activity and issues.
Adjusting Logging Levels in Flow Designer
ServiceNow allows administrators to configure flow logging levels via the system property com.snc.process_flow.reporting.level. Available levels include:
Off: No persistent flow execution details are logged.
Basic Runtime Information: Logs minimal details such as state transitions.
Full Logging: Stores complete execution details, including inputs, outputs, and status of every action.
To change the setting:
Navigate to Flow Administration > Properties.
Locate the Flow Engine Reporting property.
Select the appropriate level and save changes.
Admins should be cautious about enabling full logging in production due to potential performance impacts.
Best Practices for Flow Log Analysis and Troubleshooting
Enable Detailed Logging in Non-Production: Keep full logging enabled in development or test environments.
Use Log Actions for Custom Messages: Insert Log actions within flows to track key variables and conditions.
Implement Error Handling in Flows: Add error paths to capture and log failures proactively.
Monitor Active and Long-Running Flows: Regularly check the Active Flows list to spot any stalled workflows.
Use System Log Queries for Patterns: Search for specific error messages or flow context IDs to find related logs.
Be Aware of Log Data Retention: Flow logs are purged after a certain period, so timely analysis is key.
Logs and execution details are essential for troubleshooting in ServiceNow Flow Designer. By leveraging System Logs and Flow Execution Details, users can quickly diagnose issues, optimize workflows, and maintain automation efficiency. Adjusting logging levels strategically and following best practices ensures a smooth and well-monitored flow environment. By implementing these techniques, ServiceNow administrators and developers can proactively manage their automated workflows with confidence.
