Flow History

Flow History is the event-by-event audit trail for a flow. Use it when you need to answer practical questions such as what happened, when it happened, which contact it affected, which step produced it, and whether the action succeeded, is still pending, or failed.

Note
This document is for the History tab inside of the Flow Editor. For information on the History page, accessed through the sidebar menu, click here: History
Flow History tab with event stats and events table visible
  1. Open a flow in the Flow Editor.
  2. Click History from the editor toolbar, or open the flow modal and switch to the History tab.
  3. Review the newest events first. The table defaults to newest-first sorting by Time.
Time: Shows when the event occurred in the account timezone.
Type: Shows the event category.
Step: Shows the flow step that produced the event.
Contact: Shows the enrolled contact and available contact details.
Status: Shows whether the event is pending, successful, or in error.
  • Search, filter, sort, and paginate events with the table controls.
  • Select Refresh to load the latest event and stat-card data.
  • Export the columns currently visible in the table. Include Error when you need failure details outside DripDrop.
  • Rows with recorded interaction activity can expand to show delivery and engagement details.
  • The Step and Type values are retained on the event record. They can remain available even after the original flow block has been deleted.

Use filters first when investigating a problem, then export the filtered result if you need to share or analyze it elsewhere.

  • Text Message
  • Email
  • Pause
  • Connection
  • Conditional
  • A/B Split
  • AI

Other event types may appear as the product evolves, but the current documented set above is what the live UI explicitly filters for.

Pending: The flow action was created but has not completed yet.
Success: The action completed successfully.
Error: The action failed and needs inspection.

When you are troubleshooting, the Contact and Step columns are the fastest way to reconstruct what happened.

  • The Step tells you which block fired.
  • The Contact tells you which enrollment produced the event.
  • Together they help you move between block configuration, enrollment state, and actual execution.
  • Use Type to isolate message sends, pauses, connections, or A/B split records.
  • Use Status to focus on failures or still-pending work.
  • Use Search when you want a specific contact or step name.
  • If an event seems missing, clear the current search and filters before assuming it never happened.

Rows with recorded interaction activity can expand into the Interaction Events panel. This is where delivery and engagement details appear for the selected history record.

  • Confirmed interaction-event labels are: Delivered, Opened, Clicked, Bounced, Replied, Spam, Unsubscribed, Deferred, and Sentiment.
  • When the backend includes provider context, the panel shows the provider name as “via …”.
  • If a reply includes stored email HTML, the row becomes expandable and can show the sender, subject, and rendered reply body.
  • If no delivery or interaction records exist yet, the panel shows No delivery events recorded.
Expanded interaction events panel showing delivered opened clicked and reply details
No rows yet

The flow may not have processed any contacts yet.

Expected row missing

Clear search and filters, then check that you are looking at the correct flow.

Interaction details missing

Not every event produces interaction records, and some rows are not expandable.

Too many rows to scan manually

Filter by Status or Type first, then search for the contact or step name.

Compare execution with enrollment state

Cross-check the contact in Flow enrollments.

Confirm whether a block actually ran

Find the matching Step in History.

Find who hit an error

Filter Status to Error and inspect the Contact column.

Confirm whether a pause or connection handoff happened

Filter Type to Pause or Connection.

Need to understand email or SMS engagement?

Expand the row and review interaction events.

A contact shows an error but the cause is unclear

Inspect the related block configuration in Flow blocks or the specific flow setup in the editor.