Introduction to execution logs

Trace view

Provides an end-to-end view of a record across the entire flow run, showing how the record moved through each step and how it was processed at every stage.

When a flow includes a tool import step, the trace view displays the tool’s internal steps and nested tools, allowing you to investigate execution at each level.

The view is accessible only when a unique trace key is identified.

Step-level view

Displays the record’s execution details within a specific step (also referred to as a bubble), including the step components configured and executed in that step.

This view is available when the trace key is either not identified or is duplicated.

Logs for retry jobs

When you retry errors manually or the platform automatically retries them, each retry appears as a separate job in Run history, marked with a Retry tag.

Execution logs capture details from the step where the retry starts through the remaining steps executed in the flow. Retry jobs follow the same logging settings, payload consent, and retention period as regular flow runs.

For more information, see View logs for retry jobs.

Note: Execution logs aren't available for retry jobs that ran before execution logging was enabled.

Logs for topic flows

Topic listeners and publish steps are logged under the same execution log preferences, log level, payload consent, and retention period as the rest of the flow. Each entry opens a single Log details view instead of separate request and response sections.

• A topic listener entry shows the topic name, the timestamp, and the Offset range of the messages delivered in that page. If a replay delivered the page, the entry also shows the replay's start date and, if one was set, its end date for a Specific time replay, or Earliest for an Earliest retained replay. Replay jobs are marked with a Replay tag in Run history.
• A publish step entry shows the topic name, the timestamp, and the status code returned when the topic accepted the batch.
• At the Detailed and Debug levels, both entries also include the payload: the delivered messages for a listener, and the published records for a publish step.

Replays aren't recorded in the audit log. To see what a replay delivered, use execution logs.

For the full list of fields, see Log data captured by log level. To replay messages, see Subscribe a flow to a topic.

Log levels control the amount of execution detail captured for a flow run. Select the appropriate level based on whether you need high-level monitoring, deeper data inspection, or temporary in-depth troubleshooting.

• Basic

  • Purpose — High-level monitoring of flow execution.
  • Details captured — Step-level execution details and key information from external API calls. Payload data isn't stored.
  

• Detailed

  • Purpose — Deeper visibility for data validation and troubleshooting.
  • Details captured — Everything in Basic, plus request and response payloads and headers for external API calls.
  

• Debug

  • Purpose — Advanced, short-term troubleshooting and investigation.
  • Details captured — Complete execution details, including inputs and outputs for tool steps, mappings, transformations, and other internal components, plus full request and response payloads for external API calls.
  

• View logs for any flow run, including retry jobs and replay jobs, directly from Run history.
• Control the level of logging detail, from basic summaries to detailed or debug insights.
• Manage retention and ensure compliance for stored logs across environments.

Run logs may not be available for every flow run for the following reasons:

• When a flow processes a large volume of records and the total data size of export exceeds 1 GB, run logs are available only for the records processed before the limit was reached. Records beyond this limit appear in Trace view without log information. This limit applies to Detailed and Debug logging modes.
• Execution logs support HTTP, Salesforce, and NetSuite applications, and Celigo topic listeners and publish steps.
• When exporting large data volumes, records are processed in pages and custom scripts in the Pre-save page hook may increase the page size, causing the system to split it into multiple pages. Execution logs might not fully reflect these new pages, which can affect traceability across related steps.
• Logging is not supported for asynchronous exports and imports.
• Execution logs aren't available for retry jobs that ran before execution logging was enabled.
• Logs aren't available for deleted resources.
• Step-level debug isn't available for topic listeners and publish steps. Use the flow's Debug log level instead.

1. Select the environment you want to configure.
2. Go to Account > Company > Execution log preferences.

Basic logging — Enables or disables logging for all flows in the account. Basic logging captures essential high-level data, such as request URLs, timestamps, and status codes.

Store payload — Users can select the Detailed or Debug log level only when this setting is enabled.

Important considerations

• Store payload — Consent for capturing payloads is required and must be provided per environment. The audit log records all changes to this setting.

• Subscription — If your plan is downgraded, your log retention period automatically adjusts to match the limits of your new plan.

  Important

  The maximum retention period depends on the selected data retention. The default log retention is 30 days.

If you select Detailed log or turn on debug mode while Store payload isn't enabled for the account, a prompt asks you to notify your admin or owner.

1. Select Request admin approval to send an email request. You can resend the request once every 24 hours.

2. You receive an email notification when the request is approved or declined.

   

If you're an owner or admin and Store payload isn't enabled, the prompt instead links to Go to execution log preferences, where you can change the account setting.

To enable detailed logging as an admin or an owner:

1. Select Go to execution log preferences.
2. In Execution log preferences, turn on Store payload, and then select Save.
3. Return to the flow and select Detailed log in Change log mode.

Do not store retry data

Even if Do not store retry data is enabled in the export's Advanced section, Detailed and Debug logging store payloads once consent is given. Account-level consent always overrides this setting. A message appears when you enable Debug or Detailed logging.

A similar prompt for Do not store retry data appears in the Change log mode window when you enable Detailed logging.

Purge blob data immediately?

Even if Purge blob data immediately? is enabled in the import's Advanced section, Detailed and Debug logging store blob data once consent is given. Account-level consent always overrides this setting. A message appears when you enable Debug or Detailed logging.

A similar prompt for Purge blob data immediately? appears in the Change log mode window when you enable Detailed logging.