After a test run finishes, Flow Builder shows results for each flow step option, in the Run console, and — for scripts — in dedicated execution logs. This article covers reading all three, plus NetSuite- and blob-specific behavior. For running the test itself, see Run a flow in test mode.
Review results for each flow step option
A test result indicator appears next to each flow step option — transformation, filter, mapping, or hook — once the run completes. Select it to see the results for that step.
The Test run results panel lists every record processed by that step, along with its trace key and status:
- Success — the record was processed successfully.
- Success (ignored) — for a filter, the record was processed successfully but didn't pass the filter criteria.
- Error — the record failed.
Select a record to see the input the processor received in the Input pane, and the processor's output in the Output pane. You can only view one record at a time. Use the toggle in the top-right corner to switch the editor between Rules and JavaScript while editing.
A few behaviors to keep in mind:
- Editing the flow — changing the test source, modifying a step, changing step options, or reordering steps — clears all test run results. Run a new test to see results that reflect your changes.
- Results display only for the steps that actually ran during the test.
- For NetSuite SuiteScript hooks specifically, select Test run results to see detailed input/output. The
preSendhook only executes — and only then do its input/output appear — when no mock output has been added. - If the batch size is less than 10, the number of records shown in mock output matches the batch size. If the page size is less than the batch size, the number of records shown matches the page size instead.
- The number of records processed in a test run is based on the export's configuration.
Review test run errors
After a test completes, each processed record shows one of: Success, Ignore, Error, or Resolve — the same outcomes you'd see in a production run, indicated directly on the flow steps.
To review a record's error details:
- Select an error to open Error details and see the list of errors. The first record is selected by default, with its details shown on the right.
- Select a different record to see its error details instead.
Test run results reflect only the selected source — results aren't available for other sources you didn't test, and aren't available for dynamic lookups.
Review flow step and script debug logs
You can review a test run's debug logs — HTTP traffic for exports, imports, lookups, and listeners, plus script execution logs — without separately starting the debugger described in Debug flow steps. These are also available afterward under the regular debug logs tab.
To view script execution logs for a flow's scripts:
- On the Flow Builder page, select the Test run execution logs tab in the Run console panel.
- Select a script from the Scripts drop-down to view its log details.
postResponseMap hook execution logs aren't captured during a test run. In test mode, debug logs are available only for a single session.
NetSuite-specific behavior
If you're using SuiteBundle v1.31.0.0 and SuiteApp v1.14.0.0 or later, you can also:
- Review whether a dynamic lookup configured in NetSuite mapping produced the expected test results.
- Validate whether the results for How can we find existing records? are accurate, and adjust the criteria if they aren't.
Blob support
Blobs are supported in test run mode using updated sample data — for example, you can review a detailed test result for Handlebars expressions configured using file metadata.
If you're testing an FTP blob export or lookup and the server has more than 200 files, expect a test run delay or timeout, and results may not display.
Other considerations
- Test mode is in beta while Celigo works on improvements based on customer feedback.
- Test run data is deleted automatically when your session expires, when you run the next test in the same session, when you navigate away from Flow Builder, or when you change the URL.
- Test results don't change until you run a new test, even if you modify the flow configuration in between — and results are cleared (not saved) if you navigate away, refresh, run a new test, or enable the flow.
- Flow schedule, Next flow, auto-resolve, and error email notifications aren't available while a flow is disabled and in test mode.