This article answers common questions about execution logs and helps you understand quickly how to use them to monitor, trace, and troubleshoot your flows.
What are execution logs?
Execution logs give you end-to-end visibility into how your flows run. They show how each record is processed across all steps, helping you understand what happened during the flow run and why.
Who can use execution logs?
Execution logs are available for all Celigo users.
How do log levels work?
The log level controls how much execution detail is captured for a flow run. Choose a level based on what you need:
- Basic — Captures high-level execution details such as step status, timing, and external API calls.
- Detailed — Captures everything in Basic, plus request and response payloads and record-level context.
- Debug — Captures full, in-depth execution details for temporary investigation, including tool inputs and outputs.
Who controls the log levels?
An owner or admin is authorized to control logging at the account level. Log settings including the default log level and retention period are applied per environment.
Any user with access to a flow can enable and manage logging settings for that flow.
How do execution logs relate to other debug options?
Flow-level debug is part of execution logs. Connection and step debugging work independently of execution logs. All three are available to all customers:
What is a trace key?
A trace key uniquely identifies a record during a flow run and helps you track the record across every step in the flow.
You can also search run history using the trace key to quickly locate a specific record.
Can I view execution logs for tools used in flows?
Yes. When a flow includes a tool import step, you can view the tool's input, output, internal steps, and nested tools in the trace view. Tool logs follow the parent flow's log level, permissions, and retention settings. If a unique trace key is available, you can trace a record across the flow and its tools.
For more information, see View flow run logs.
Can logs be deleted?
Yes. You can delete logs from the Run history page. Deleting logs removes stored log data and payloads but does not remove the run history or error records.
Are execution logs captured for retry jobs?
Yes. When you retry errors, or the platform auto-retries them, the retry job captures execution logs the same way a standard flow run does. It uses the same log level, payload consent, masking, and retention settings. The logs start at the step where the retry began, and a Retry tag shows that you are viewing a retry job. Retry jobs that ran before retry logging was introduced don't have logs.
Will retry jobs increase my log storage?
They can. If your flows retry errors often, each retry job adds to your stored log data. Retry jobs follow the same log level and retention settings as standard flow runs, so you can manage storage with those settings.
Are execution logs captured for topic flows?
Yes. Topic listeners and publish steps follow the flow's log level, payload consent, and retention settings. A listener entry shows the topic name, timestamp, and offset range of the delivered messages. A publish step entry shows the topic name, timestamp, and status code. At the Detailed and Debug levels, both include the payload. Step-level debug isn't available for topic steps.
For details, see Log data captured by log level.
How can I tell whether a replay delivered a page?
In Run history, replay jobs are marked with a Replay tag. In Trace view, a topic listener entry for a page a replay delivered shows Replay details with 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. Replays aren't recorded in the audit log.
Does the publish step's status code mean every record was published?
No. The status code shows that the topic accepted the batch. Records that failed appear in error management.
Is execution logging supported for integration apps?
Yes, at the Basic level only.