Flow Designer lets you test flows against real records before deploying them to production. This guide shows you how to run test executions, step through each action, and trace errors back to specific steps.
Why testing flows before deployment matters
Flows that look correct in the designer often fail when they hit real data — missing field values, permission issues, or logic that works for one record type but breaks on another. Without testing, you discover these problems when users start complaining or when you're debugging failed executions in production. Platform developers and admins end up spending more time troubleshooting live flows than building new ones, especially when the failure happens three steps deep in a complex flow.
How flow testing works
Flow Designer's test mode runs your entire flow against a record you choose, but logs every step so you can see what happened. You pick a test record that represents realistic data, hit Test, and watch each action execute in sequence. The execution details show you input values, output values, and any errors that occur. The key insight: test runs aren't simulations — they perform real actions against real records, including sending emails and updating databases.
Building confidence through systematic testing
Start by testing happy path scenarios with clean data, then test edge cases like missing values, locked records, or users without permissions. Test different record states — new records, records with related data, records that other processes have touched. Advanced flow developers create dedicated test records that cover common failure scenarios, and they suppress notifications during testing to avoid spamming users while debugging.
Before you start
- •flow_designer role or admin role
- •Access to records that match your flow's trigger conditions
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Open your flow for testing
Navigate to Flow Designer > Designer and open the flow you want to test. Click the Test button in the top toolbar — it's next to Activate. The test panel opens on the right side of the screen.
If Test is grayed out, save your flow first — you can't test unsaved changes.
Select a test record
In the test panel, click Choose Record to pick the record your flow will run against. Search for a record that has realistic data — avoid empty records or ones with unusual values. The record you pick should match the table and conditions your flow expects.
Create dedicated test records with known data rather than using random production records.
Suppress notifications if needed
Before running the test, decide whether you want notifications to fire. If your flow sends emails or creates notifications, toggle 'Suppress Notifications' to prevent test runs from spamming real users. Leave it unchecked only when you specifically need to test the notification behavior.
Execute the test run
Click Run Test to start execution. The flow runs in real-time against your chosen record. Watch the progress indicator as each step completes. When execution finishes, you'll see either a green success message or a red error indicator.
Test execution can take several seconds for complex flows — don't click Run Test multiple times.
Review step-by-step execution details
Click View Execution Details to see what happened in each step. The execution log shows every action that ran, the data that flowed between steps, and the final outputs. Green checkmarks indicate successful steps, red X marks show failures, and yellow warnings highlight potential issues.
Expand each step to see input and output values — this is where you'll spot data transformation problems.
Debug failed steps
When a step fails, click on the red error indicator to see the specific error message. Common failures include permission errors, missing field values, or invalid data transformations. The error details tell you exactly which line of script or which field caused the problem.
Look at the inputs section first — most flow errors happen because expected data is missing or in the wrong format.
Verify real system changes
Check that your test run made the expected changes to your ServiceNow instance. If the flow updates records, creates tasks, or sends notifications, verify those actions completed correctly. Remember that test runs count toward usage metrics and create real audit trail entries.
Best practices
Test with records that have missing or null values in key fields — flows that work with complete data often break when fields are empty.
Always suppress notifications during debugging unless you're specifically testing email or notification logic.
Create a dedicated test user account with limited permissions to verify your flows handle access control correctly.
Test runs increment counters and create audit entries — don't run the same test dozens of times against production records.
Save successful test executions as documentation — the execution details show other developers exactly how data flows through your process.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue