Once logging is active and your flow has executed, you can access the run logs directly from the run history for each record.
Following are the Run log column details:
-
Timestamp: Start time of each step.
-
Status: Record status – Success, Failed, or Ignored.
-
Step: Name of the flow step (Export, Lookup, Import).
-
Application: Connected application for the step.
-
Duration: Time taken to complete the step.
-
Trace key: Unique identifier for tracking records across the flow.
-
Open trace view: Trace view for the selected record.
To view run logs:
-
Go to your Flow > Run history.
-
Click the Run logs icon adjacent to the flow step.
-
In the Run Logs page you can see the run logs for all the executed records in the flow run.
-
You can filter steps to show only those traversed by the record.
-
Click the Open trace view icon adjacent to the flow step.
Important
Sensitive information like authentication tokens or API keys are always masked.
-
In the Trace view, you can see the step-by-step execution for each record.
Note
If a record has a duplicate trace key, you’ll see a Duplicate badge next to the trace key.
For records without trace keys, duplicated trace keys, or if a record can’t be traced, then only the details for the selected step or record from the Run logs page are shown.
You can now search and filter flow run history using specific criteria to quickly locate relevant runs and analyze targeted subsets of data. These options help you narrow down records, identify child records in one-to-many scenarios, and open run logs already filtered to your search. You can filter or search run history using Trace key:
-
Search using full trace keys (or partial (prefix))
-
Supports child trace keys in one-to-many cases (parent key + child key).
Important
File exports do not support searching inside file content. Use the trace key instead.
You can search and filter flow run log using specific criteria to quickly locate relevant runs and analyze targeted subsets of data. These options help you narrow down records, identify child records in one-to-many scenarios, and open run logs already filtered to your search.
Note
The search works same in the Run history page and Run logs page.
The following options are available to help you narrow down the displayed flow run records:
-
Step: Filter runs based on the specific step within the flow where the execution was logged or where a particular event occurred. This is especially useful for analyzing long or multi-step flows.
-
Status: Filter logs by the final outcome of the flow run, such as success, ignored, or failed. This allows for immediate focus on successful or problematic executions.
-
Application: Narrow the log entries to only show runs associated with a specific integrated application (NetSuite and HHTP) involved in the flow.
For one-to-many, a single parent record expands into multiple child records, and the UI lets you drill down into each child’s execution details at the step where the split happens. At the flow step level where one-to-many lookup or import are configured, the UI shows a subset or list of child records that were created/looked up from the parent.You can filter those child records by the status: success or ignored or error.
Selecting a child record takes you straight to its Trace view, allowing you to trace its execution across steps.
If no items match your criteria, the screen displays a clear message prompting that the records are not available.
When a record fails to process successfully, you can locate that record in the list and click the Open trace view icon. The trace view provides a comprehensive, step-by-step account of the record's journey through the system including any errors, warnings, or detailed diagnostic information that led to its failure.Click the Open trace view icon for a specific failed record to view the error log details.
If you wish to see further details, retry or resolve click the View error on the left side of the screen. It's a link redirecting you to the error management dashboard, where you can view the failure details and take necessary action.
Logs are automatically deleted based on your chosen retention period. All changes to retention periods are recorded in the account audit logs.
-
Log types (Basic, Detailed, Debug)
-
Payload consent approvals
-
Retention period updates
It ensures full traceability and compliance with data governance policies.
Note
Audit logs cannot be modified or deleted.
You can delete stored flow run logs and payloads to reduce retained data or meet compliance requirements. Purging permanently deletes the selected log data while preserving flow run history and error information.
You can delete flow run logs to remove data that is no longer required or must be deleted for compliance. Purging allows you to selectively delete stored logs and payloads while preserving job history and error information.
From the Run history tab, users can delete logs for selected runs (or a set of runs). The delete deletes all stored data related to that selection, including logs and payload. Even after purging, the jobs in run history remain and error information is preserved (so run history doesn’t disappear). You can choose a date range to delete multiple logs within that period.
Note
The jobs that are completed within the selected timestamp are only deleted.
If you executed a flow multiple previously and have executed again while the delete is taking place, then only the previous flow run logs will be deleted and the current flow run is excluded.
Use the following steps to delete a log:
-
To delete a log you must navigate to Flow > Run history > Click Delete logs.
-
Select the date range and click Apply.
-
In the Delete logs? window, click Delete logs .
Each delete action is recorded in the Audit Logs with details such as time, user, action, and the selected date range.
Log deletion is restricted to the following users only:
-
Admin
-
Owner
-
Users with manage access (all integrations or specific integrations)