Most issues show up in the Activity view — comparing where records ended up against what you expected is the fastest way to find the problem. Here are the common ones.
Nothing enrolled / the run is empty
A schedule workflow hasn't fired yet. Check the trigger's "Next 5 runs", and that the workflow is Live.
A Companies from segment run found nothing new. Companies from segment enrolls incrementally, so once a segment is exhausted a run brings in zero new companies. That's expected — widen the segment or lower expectations.
A search returned nothing. Loosen the sourcing step's filters and confirm the limit is above zero.
Net new excluded everything. Company search, People search, and the lookalike steps skip records already in a lead list, an export, your CRM, or that the step already enrolled on a previous run, whenever Net new is on. A search can match real records and still enroll zero if every match falls into one of those. Turn Net new off to confirm, or check the record directly in your CRM/Leads/exports to see which exclusion applies.
A run stopped partway through
A run that runs out of credits, hits a failed upstream step it can't recover from, or gets rate-limited can stop before every record finishes. This is different from a record failing at one step — here the run itself doesn't reach the end.
Whatever finished before the run stopped is not lost — it's visible per record in Activity.
A run that reaches a delivery step no longer leaves you guessing: Runs always shows either the result (a link, a count) or the stated reason there isn't one — "Out of credits", "Run limit reached", "No records reached this step", and so on — plus how many records are missing if the run only partially delivered.
Records held up specifically by running out of credits show as Blocked in Activity, not Failed — they're not stuck permanently, they resume automatically once credits are topped up and the workflow is unpaused.
Check the workflow's status for why it stopped — most often Ran out of credits. See Activate, pause, and run limits.
Top up credits (or otherwise fix the cause), then resume the workflow — blocked records pick up on their own. If you need a file covering every record enrolled in the run so far, regardless of how it ended, use Download report on the run's page rather than waiting on a barrier step like Generate CSV link, which only produces something once the whole run finishes.
Too many records dropped
Open the filter or route and check the conditions.
Check the and / or setting — "and" requires every condition, "or" needs just one. This is the most common cause.
Confirm the condition tests a field an earlier step actually produced. See Build conditions.
A route sends everything the wrong way
Route uses the first matching branch. Put your most specific conditions first, and leave a final branch with no condition as the catch-all so nothing drops unintentionally.
An @-mention is empty or a condition never matches
An @-mention resolves per record. If the step that produces it didn't run for a record — it dropped earlier, or the step found nothing — the value is empty.
Make sure the producing step is above the one referencing it.
Filter out records that won't have the value before the step that needs it.
Confirm the field name matches the producing step's output exactly.
A step shows "Failed"
CRM, Slack, or sequencer steps: the tool likely isn't connected. See Connect your tools.
HTTP request: the endpoint returned a non-success response. The failure reason is in the record's step detail in Activity.
A record stopped at a step I don't mind failing
By default, a record that fails at a step stops there and is reported as failed, rather than carrying on and finishing green further down. That's usually what you want — a silent failure is worse than a visible one.
When a step's failure is genuinely tolerable — an optional enrichment, a best-effort notification — turn on Continue on failure in that step's settings and records will carry on to the next step even if it fails.
It's available on the steps that call out to something and can therefore fail: AI research, Google search, Crawl website, Compare websites, Parse JSON, HTTP request, Notify, Add to sequence, Send companies to CRM, and Send people to CRM.
The workflow won't publish
One or more steps still need setup and are flagged red. The Publish button says how many. Open each red step, complete its settings, then publish. A Delay step needs a duration greater than zero.
The workflow paused itself
If it shows "Paused · run limit reached", it hit the run limit in its Settings. Raise or clear the limit. See Activate, pause, and run limits.
It runs more often — or less — than expected
Check the trigger. For a schedule, confirm the frequency (Daily, Weekly, or Monthly), the days or dates it's set to, and the time zone, and read the "Next 5 runs" preview. For event triggers, remember multiple events combine as "or" — any one of them starts a run. See Triggers.
Still stuck?
Open the record in Activity and read its step-by-step detail — the input and output at each step usually shows exactly where things diverged from what you expected.