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 an end to end visibility into how your flows run. It shows 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.
What are logs and how do logs level work?
Log level controls how much execution detail is captured for a flow run. Choose the level based on your need.
- Basic: Captures high level execution details such as step status, timing, and external API calls.
- Detailed: Captures everything in basic, request or response for payload 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 authorised 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 flow can enable and manage logging settings at the flow level.
Has the existing debug functionality been modified?
We have added the new debug functionality at the flow level, while the existing debug capabilities remain the same. Following are the options available debug:
- Debug a connection - Available to all customers (existing feature and no changes made)
- Debug a step - Available to all customers (existing feature and no changes made)
- Debug a flow - Available to all customers (new feature as part of execution logs functionality)
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. Logs can be deleted 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 this release do not 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.
Is execution logging supported for Integration apps?
Yes, only the Basic log mode is supported.