The tables describe the log data captured for flow runs based on the selected log level (Basic or Detailed) and the type of application used in a flow step. Understanding this helps you know what execution details are available when reviewing run logs for exports, lookups, and imports. The same data is captured for retry jobs at each log level. For Celigo topic listeners and publish steps, see Celigo topics.
The following table outlines the generic execution details captured at the record level for all supported applications.
Log level |
Export / Lookup |
Import |
Basic |
• Record status (Success / Ignored / Error) • Record start and completion timestamps • Time taken at each bubble (step) • Trace key |
• Record status (Success / Ignored / Error) • Record start and completion timestamps • Time taken at each bubble (step) • Trace key |
Detailed |
• Everything included in Basic |
• Everything included in Basic |
Note
Generic details are always captured at the record level, regardless of application type.
The following table describes additional details captured for HTTP-based and NetSuite SuiteScript 1.0 applications, including JSON, XML, Webhooks, and Blob-based operations. These details vary by log level and operation type.
Log level |
Export / Lookup |
Import |
Basic |
• Request URL with HTTP method • Status code • Export data URI |
• Request URL with HTTP method • Status code • Import data URI |
Detailed |
• Everything in Basic • Request payload • Response payload • Request and response headers |
• Everything in Basic • Request payload • Response payload • Request and response headers |
Log level |
Export / Lookup |
Import |
Basic |
• File path with filename and type • File created date and time • File size |
• File path with filename and type • File size |
Detailed |
• Everything in Basic • Raw response received from the application (selected format) |
• Everything in Basic • Raw request sent to the application (selected format) |
Warning
Run logs larger than 10 MB aren't displayed. Use the download link to view them offline.
Key notes
- Detailed logs always include everything captured in basic logs, plus payload-level and header details.
- Payloads and headers are available only when Detailed log is selected and permitted.
- Sensitive fields (such as tokens or credentials) are masked in all log levels.
- For batch or file-based operations, the same request or response may apply to multiple records.
The following tables explain the execution details captured for NetSuite-based flow steps at each log level. These logs help you understand how records are processed in NetSuite, troubleshoot issues, and validate execution behavior.
Log level |
Export / Lookup |
Import |
Basic |
Real-time: • Same details as NetSuite webhooks • Error details if a preSend hook fails Scheduled: • Export data URI • Response status |
• NetSuite API endpoint used (with HTTP method) • Status code • Import data URI |
Detailed |
• Everything in Basic • Time taken for scripts and hooks • PreSave page execution time • PreSend page execution time • Search filters used and search execution time • Request payload with headers • Response payload with headers |
• Everything in Basic • Conditional, operational, and dynamic lookup request/response payloads (batched) with execution time • Time taken and status for NetSuite hooks • Time taken to process the record in NetSuite • Request payload with preMap data • $R profile used to process the record • Response payload with headers |
Log level |
Export / Lookup |
Import |
Basic |
• File path with filename and type • File created date and time • File size |
• File path with filename and type • File size |
Detailed |
• Everything in Basic • Raw response from NetSuite (Base64) • Headers |
• Everything in Basic • Raw request sent to NetSuite (Base64) • Headers |
Salesforce
The following tables describe the execution details captured for Salesforce-based flow steps at each log level. Use these logs to verify how records are processed in Salesforce, troubleshoot issues, and validate request and response behavior across Salesforce API types (SOAP, REST, Composite, and file-based operations).
Note: This section describes Salesforce steps in flows. For Salesforce steps in APIs built with API builder and in tools, see View API request and execution logs in API builder and View tool invocation logs.
Salesforce export, lookups, and imports
| Log level | Export / Lookup | Import |
| Basic |
|
|
| Detailed |
|
|
Blobs
| Log level | Export / Lookup | Import |
| Basic |
|
|
| Detailed |
|
|
Celigo topics
The following table describes the execution details captured for topic listeners and publish steps at each log level. Each entry opens a single Log details view with General details, Replay details (topic listeners only), and Payload sections. There are no separate request and response sections.
| Log level | Topic listener | Publish step |
| Basic |
• Topic name • Timestamp • Offset range of the messages delivered in the page • Replay details, when a replay delivered the page: the start date and, if one was set, the end date for a Specific time replay, or Earliest for an Earliest retained replay |
• Topic name • Timestamp • Status code |
| Detailed |
• Everything in Basic • Payload: the topic name, offset range, and delivered messages |
• Everything in Basic • Payload: the published records |
Key notes
- At the Debug level, topic steps capture the same details as Detailed.
- The publish step's status code shows that the topic accepted the batch. It doesn't confirm each record. Records that failed appear in error management.
- Replay details appears only for pages a replay delivered.
- Payloads appear only when Store payload is enabled in Execution log preferences.