Triggered flow shows 0 contacts

If a triggered flow that previously processed contacts suddenly drops to zero, the issue is almost never the flow configuration itself. Here's how to diagnose it.

Step 1: Check the trigger dataset

Go to Datasets and open the dataset powering your flow's trigger. Check when it last successfully ran. If the dataset hasn't refreshed recently, or its last run shows an error, that's the root cause — the flow has no new events to process.

Step 2: Check the entry segment

If your flow uses an entry segment in addition to the trigger event, open that segment and check its current contact count. If the segment evaluates to zero — due to a logic change, a data issue, or an expired time filter — no contacts will enter regardless of how many trigger events fire.

Step 3: Check for paused or erroring upstream queries

Navigate to Datasets > [Your Dataset] > Queries and confirm none of the underlying queries are failing or paused. A failing query silently halts the dataset refresh without always surfacing a visible alert in the flow UI.

Step 4: Check flow configuration changes

Review the flow's version history to see if any recent changes — schedule adjustments, entry criteria edits, audience filters — may have inadvertently restricted contact entry.

📘

Key concept

A triggered flow's health depends entirely on its upstream data. Zero contacts entering is a data signal, not a flow signal. Start your investigation at the dataset layer, not the flow layer.