Skip to content

Bot Logs

Every LeadPattern bot run is logged step by step — use Bot Logs to see what a bot did, whether it completed, paused or errored, and troubleshoot missed replies.

2 min readUpdated Oct 5, 2026

Every time a bot runs, LeadPattern records it. The Bot Logs are your window into what actually happened — which steps ran, in what order, and how the run finished. When a customer didn't get the reply you expected, this is where you look first.

What a log shows

Each run is one log entry, and it captures the steps the bot took along the way:

  • Which trigger started the run and for which contact.
  • Each step the flow executed, in order.
  • How the run finished.

How a run can finish

Completed

The flow ran to the end with no errors.

Stopped

The run paused — either at a delay or wait step, or while waiting for an interactive reply. It will resume when the delay elapses or the customer taps an option.

Errored

Something went wrong during a step. The log shows where it stopped so you can fix the node.

Troubleshooting with logs

1

Check that a run started

If there's no log for the contact, the trigger didn't fire — the bot may be inactive, or the event didn't match its trigger.

2

Find where it stopped

Read the steps in order. A run that's stopped is waiting on a delay or a reply, not broken.

3

Look for an error step

An errored run points at the node that failed — open that node in the builder and check its settings.

4

Confirm priority

If an interactive reply was in progress, remember that tap is handled first and can skip your on_message bots for that message.

What's next

Was this article helpful?

Your feedback helps us continuously improve our documentation.

Need more help with this topic?Ask LeadPattern Support

Related Articles