View flow run logs

After logging is on and your flow has run, you can open the run logs for each record from Run history.

The Run logs page shows these columns:

• Timestamp — Start time of each step.
• Status — Record status: Success, Failed, or Ignored.
• Step — Name of the flow step, such as an export, lookup, import, tool import step, topic listener, or publish step.
• 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 — Opens Trace view for the selected record.

To view run logs:

1. Open the flow and select Run history.

2. Select the Run logs icon next to the flow step.

   
3. The Run logs page shows the run logs for all records processed in the flow run.

4. Optional: filter steps to show only those the record passed through.

   

5. Select the Open trace view icon next to the flow step.

   

   Important

   Sensitive information, such as authentication tokens and API keys, is always masked.

6. Trace view shows the step-by-step execution for the record.

   

For records without trace keys, records with duplicated trace keys, or records that can't be traced, only the details for the selected step or record from the Run logs page are shown.

View execution logs for tool import steps

When a flow includes a tool import step, trace view shows what happened inside the tool. This includes the tool's input and output, its lookups and imports, and internal components such as filters, transformations, mappings, and hooks.

1. Go to your flow, and then select Run history.
2. Select the Run logs icon next to the tool import step.
3. Select the Open trace view icon for the record you want to investigate.
4. Expand the tool import step to view its internal steps and any nested tools.
5. Select a step to review its execution details.

You can investigate and resolve errors in tool steps and nested tool steps directly from the flow.

Note: Tool logs follow the parent flow's log level, permissions, and retention settings. At the Basic level, payloads aren't stored, so tool input and output data doesn't appear. A unique trace key lets you follow a record across the flow and its tools. Without one, you can still view the available step-level details.

View execution logs for topic listeners and publish steps

When a flow subscribes to or publishes to a Celigo topic, each topic step has its own log entry.

1. Go to your flow, and then select Run history.
2. Select the Run logs icon next to the topic listener or publish step.
3. Select the Open trace view icon for the entry you want to investigate.
4. In Flow path, select the topic listener or publish step. Log details shows these sections:
   • General details — For a topic listener: Topic name, Timestamp, and Offset range. For a publish step: Topic name, Timestamp, and Status code.
   • Replay details (topic listeners only) — For a Specific time replay, the Start date and, if one was set, the End date of the replay that delivered the page. For an Earliest retained replay, Earliest. This section appears only for pages a replay delivered.
   • Payload — The delivered messages or published records. Appears only at the Detailed and Debug levels.

Note: The publish step's status code shows that the topic accepted the batch, not that every record succeeded. Records that failed appear in error management. Each replay runs as its own job, marked with a Replay tag in Run history.

View logs for retry jobs

You can view execution logs for manually triggered retry jobs from Run history. Each retry appears as a separate job with a Retry tag.

To view logs for a retry job:

1. Open the flow and go to Run history.
2. Locate the job marked with a Retry tag. The Triggered by column shows who initiated the retry.
3. Select the Run logs icon next to the flow step.
4. Select Open trace view for a record to view its execution details.

The logs show only the steps executed during the retry, starting from the step where the retry began.

In Trace view, earlier steps and branches are collapsed and disabled. You can expand and navigate through the steps executed during the retry. If you open logs from a specific step, Trace view opens at that step.

Note:

• Automatically retried records do not appear as separate jobs in Run history.
• If a unique trace key is unavailable, only step-level details are shown.
• Retry jobs display a Debug tag when Debug logging is enabled.
• Logs are unavailable if logging was disabled, the retention period has expired, or the retry occurred before retry logging was introduced.

To review or manage retry errors, see Monitor and manage retries.

Search and filter run log

You can search and filter the flow run log by specific criteria to 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

Search works the same way on the Run history and Run logs pages.

The following options are available to help you narrow down the displayed flow run records:

• Step — Filter runs by the step where the execution was logged or where a particular event occurred. This is especially useful for long or multi-step flows.
• Status — Filter logs by the final outcome of the flow run, such as success, ignored, or failed.
• Application — Show only runs associated with a specific application in the flow, such as NetSuite or HTTP.

Filter one-to-many lookups or imports

In a one-to-many lookup or import, a single parent record expands into multiple child records. At the step where the split happens, you can drill down into each child record's execution details. The step lists the child records created or looked up from the parent, and you can filter them by status: success, ignored, or error.

Selecting a child record takes you straight to its Trace view, allowing you to trace its execution across steps.

If no records match your criteria, a message says that no records are available.

View and resolve log errors

When a record fails, locate it in the list and select the Open trace view icon. Trace view shows a step-by-step account of the record's path through the flow, including any errors, warnings, or diagnostic details that led to the failure.

To see more details, retry, or resolve the error, select View error on the left side of the screen. It opens the error management dashboard, where you can review the failure and take action. See Intro to error management.