Home 🔁 Flows Building 📜 Using Flow Logs for Troubleshooting

📜 Using Flow Logs for Troubleshooting

Last updated on Feb 05, 2026

Article content

Flow Logs in Flows Building provide a record of how flows run, including when they trigger, what actions execute, and where failures occur.

Using Flow Logs is one of the most effective ways to troubleshoot unexpected flow behaviour.

What Are Flow Logs?

Flow Logs record information about each flow run, such as:

  • When a flow was triggered

  • Which steps were executed

  • Data passed between steps

  • Errors or failures encountered

Logs help you understand what happened, not just what you expected to happen.

When to Use Flow Logs

You should review Flow Logs if:

  • A flow is not triggering

  • An action fails

  • A flow behaves differently than expected

  • Issues occur intermittently

  • You need evidence for troubleshooting or support

Flow Logs are especially useful after recent changes.

Accessing Flow Logs

To view Flow Logs:

  1. Open Flows Building

  2. Select the relevant flow

  3. Open the Logs or Execution History section

  4. Choose a specific run or time period

Log availability may vary depending on your configuration.

Understanding Log Entries

Each log entry typically shows:

  • Trigger details

  • Step-by-step execution order

  • Inputs and outputs for each step

  • Error messages, if any

Reading logs from top to bottom shows how the flow progressed.

Identifying Common Issues in Logs

Flow Did Not Trigger

  • No log entry exists

  • Indicates the trigger never fired

Check trigger conditions and event timing.

Flow Triggered but Stopped Early

  • Log shows trigger but no subsequent actions

  • Often caused by failed conditions

Review condition logic and data values.

Action Failed

  • Log entry includes an error or failure state

  • Often linked to configuration, data or permissions

Check action setup and required fields.

Using Logs to Isolate Problems

To isolate issues:

  • Compare successful and failed runs

  • Look for differences in input data

  • Identify the exact step where execution stops

Logs help pinpoint where logic or configuration breaks down.

Best Practices for Using Flow Logs

  • Review logs after publishing changes

  • Save examples of failures for reference

  • Use logs before contacting support

  • Combine logs with configuration review

Logs are most effective when used early in troubleshooting.

What Flow Logs Don’t Show

Flow Logs may not include:

  • Detailed third-party system errors

  • External system internal logs

  • Network-level issues

Some failures may require checking external systems separately.

When to Contact Support

Contact Pickle Support after reviewing Flow Logs if:

  • Errors are unclear or unexplained

  • Logs indicate a system-level issue

  • Behaviour differs from configuration

When contacting support, include:

  • Flow name

  • Log timestamps

  • Relevant log excerpts

  • Description of expected vs actual behaviour

This helps speed up investigation.

Related Articles

  • Troubleshooting Flows That Are Not Triggering

  • Troubleshooting Actions That Fail

  • Understanding triggers, conditions & actions

  • How to Get Support for Flows Building