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 Segment TAM run found nothing new. Segment TAM 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.
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.
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 Wait 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 interval, weekdays, and 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.