The enhanced logging capability delivers enterprise-grade visibility into flow execution, providing a unified and consistent view of how each record is processed across environments in an account. You can trace records end to end through every step, quickly locate relevant runs using searchable history, and troubleshoot issues with clear step-level insights.
Note
Basic execution logging is enabled by default for all accounts. You can change the log level any time as required.
You have configurable log levels, such as:
-
Basic for high-level execution details
Note
Integration apps support only Basic logging.
- Detailed for deeper request and record context
- Debug for temporary in-depth investigation
Important
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 only to 2024 pricing customers (new feature as part of execution logs functionality)
These logs enable you to capture the right level of information based on your operational needs.
See the following video for more detailed information:
An owner or admin can control the log level at the account level using account preferences. You can enable logs for individual flows, the default log type and retention period for your entire account is applied per environment.
Log in using an owner or admin credentials, in the Home page on the top right click the avatar icon and select Execution log preferences.
The Run logs feature provides complete, transparent visibility into every step of your flow's execution. You can review the specific data, payloads, and records processed during each run, which helps you:
- Verify results: Confirm your flows are working as expected.
- Trace records: You can use the record trace key to confirm whether a specific record was processed by Celigo or not. This option helps you identify if the record was ignored during execution, or verify if the record was successfully submitted to Celigo for processing.
- Troubleshoot issues: Quickly identify errors and access payload details for debugging.
- Track records: Effectively track records as they move through exports, lookups, imports, and internal step components.
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.
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.
Log levels control the amount of execution detail captured for a flow run. The flow run execution details are captured based on the log levels you set. 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. Does not store payload data.
-
Detailed
-
Purpose: Deeper visibility for data validation and troubleshooting.
Details captured: Includes everything in Basic, plus request or response payloads and headers for external API calls.
-
Debug
-
Purpose: Advanced, short-term troubleshooting and investigation.
Details captured: Complete execution details, including inputs or outputs for internal step components (like mappings and transformations), and full request/response payloads for API calls.
- View logs for any flow run 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 different 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.
- Currently, HTTP and NetSuite applications are supported.
- 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. Due to a current limitation, execution logs may not fully reflect these newly created pages, which can affect traceability across related steps.
- Logging is not supported for asynchronous exports and imports.
- Logs are currently not captured for retry jobs.
- Logs are not available for the deleted resources.
Note
Only admins and owners are authorized to set up account-level logging preferences. If you want basic logging, you can use this setting or else configure/change log mode for each flow.
- Select the environment you want to configure.
- Navigate to My account > Execution log preferences.
Note
Preferences are set individually for each environment.
Basic logging: You can enable or disable logging for all flows in the account. Captures essential high-level data, such as request URLs, timestamps, and status codes.
Note
The logging preferences can be changed at flow level settings.
Store payload: Only on enabling this setting users will be authorized to enable the log mode to Debug or Detailed log type.
Note
To store payloads for deeper insights, you must grant consent to manage and monitor users. This action is automatically recorded in the account audit logs.
Important considerations
- Store payload: Consent for capturing payloads is required and must be provided per environment. All changes to this setting are tracked in the audit logs.
-
Subscription: If your plan is downgraded, your log retention period will automatically adjust to match the limits of your new plan.
Important
The maximum retention period will be based on the selected data retention. By default, the log retention is maintained for 30 days.
Tip
You can also choose not to capture or save any logs for a flow, that is, choose No logging as an option.
You can capture the right level of detail based on your troubleshooting or monitoring needs and log levels available based on your subscription.
To change the log mode or level:
- Navigate to a flow.
-
On the right end of the page click (...) and select Change log mode.
- Choose one of the following options and click Save:
-
Same as account level (Basic logging) – Uses the log type defined in Execution log preferences.
Basic logging – Logs summary-level data per step.
Detailed logging – Logs complete request and response payloads.
No logging – Disables logs for this specific flow.
If you try to select Detailed or Debug without account-level consent:
- A prompt message to notify your admin or owner is displayed if the Store payload is not enabled.
- Click Request admin approval to send an email request.
- You can resend this request once every 24 hours.
-
You will receive an email notification once the consent request is approved or declined.
Account owners or admins who initially logged in using Basic logging can change their log level preferences. If they wish to do so, a prompt will appear with a link, Go to execution log preferences redirecting them to change the logging preference.
To enable detailed logging as an admin or an owner:
- Click Go to execution log preference.
- In the Execution log preference, enable the Store payload option and click Save.
- Return to the flow and select Detailed logs from the Execution log preferences.
Even if Do not store retry data is enabled in the export's Advanced section, enabling detailed or debug logs will still result in the storage of payloads once consent is given. Note that account-level consent always overrides this setting. You will be prompted with a message while enabling Debug and Detailed logging.
You will see the similar prompt for Do not store retry data in the Change log mode window while enabling the Detailed logging.
Even if Purge blob data immediately? is enabled in the import's Advanced section, enabling detailed or debug logs will still result in the storage of blob data once consent is given. Note that account-level consent always overrides this setting. You will be prompted with a message while enabling Debug and Detailed logging.
You will see the similar prompt for Purge blob data immediately? in the Change log mode window while enabling the Detailed logging.
You can temporarily enable debug logging to capture deeper insights into flow execution. Debug mode records all request/response payloads, tool inputs/outputs, and transformation data.
Note
Irrespective of the selected log preference, enabling debug mode will override that setting, and the flow will execute exclusively in debug mode.
You are allowed to run a flow in debug mode for based on the option you select from the table below:
| Subscription | Maximum debug duration |
|---|---|
| Free trail | 15 mins |
| Standard | 1 hour |
| Professional | 24 hours |
| Enterprise | 72 hours |
The minimum time you can run a flow in debug mode is 5 mins and the maximum is based on your subscription.
To set Debug mode:
Switching between log levels or enabling debug mode is captured in the audit logs for traceability.
Important
The Detailed and Debug modes remain disabled until an admin or owner grants payload consent at the account level by enabling Store payload setting.