Overview
Check the automation's own activity before changing anything. REsimpli records what happened, and guessing wastes time you do not need to spend.
There are four usual causes:
The trigger never occurred
The lead was never enrolled
A step is misconfigured
On a legacy plan, the account ran out of messaging or email credits
Steps
Step 1: Open the automation
Step 2: Check Automation Enrollment
Did the lead actually enter the automation? If it never enrolled, the problem is the trigger, not the sequence.
Step 3: Check Automation Activity
This shows the most recent step that executed — how far the sequence actually got.
Step 4: Check the trigger conditions
Compare them against what really happened on the lead. A status-change trigger, an activity trigger, and manual assignment are three different things, and a lead that met one has not necessarily met another.
Step 5: Check the next step
Look at its delay, its action, and any settings it needs. A step waiting on a delay has not failed.
Step 6: Check credits, on legacy plans
Accounts still on credit-based plans need available messaging and email credits. A step can sit pending because there are none. Enable auto-renew if you want to avoid it recurring.
Step 7: Check A2P, if the first SMS is involved
See How to Add A2P 10DLC Language to an Automation.
Step 8: Test again with a sample lead
Trigger it the way it is meant to be triggered. Opening a lead and waiting does not fire a status-change automation.
Tasks are a special case
Since 7 October 2026, all of an automation's tasks are created the moment the lead enters it — including tasks scheduled for future dates.
Two things follow from that when you are diagnosing:
Seeing the tasks does not mean the sequence is running. They were all created at enrolment. Check Automation Activity for what has actually executed.
Tasks remain if the automation is stopped. A lead carrying tasks from an automation that is no longer running is expected, not a fault.
Reading the symptom
What you see | What it usually means |
Lead not in Automation Enrollment | The trigger did not fire, or its conditions were not met |
Enrolled, but stopped partway | Look at the next step — delay, configuration, or a missing resource |
Step showing pending | Often a required resource is unavailable, such as exhausted credits on a legacy plan |
Tasks present but no messages sent | Normal — tasks are created upfront. Check Automation Activity for executed steps |
Important Notes
Automation Activity is the fastest way to see how far the workflow progressed.
A pending step usually means a missing resource, not a broken automation.
Test the exact trigger. Most "it did not run" reports are a trigger that was never fired.
Unlimited 6.0 plans do not use messaging credits — step 6 applies to legacy credit-based plans only.
Tasks appearing early is not evidence the automation is working. They are created at enrolment regardless.
Frequently asked questions
Why is the step showing pending?
On a legacy credit-based plan, exhausted SMS or email credits are a common cause.
How do I know whether the lead entered the automation?
Check Automation Enrollment.
Where can I see the last step that ran?
Automation Activity.
All the tasks appeared at once. Did the whole automation already run?
No. Tasks are created upfront when the lead enters the automation. The messages still send on their scheduled delays.
Troubleshooting checklist
Is the automation active?
Did the trigger actually occur?
Is there a delay before the next step?
Are credits available, where applicable?
Is the A2P setup correct on the first SMS step?
Does the step have a valid sending number? See How SMS Sending Numbers Work Inside Automations.
Related
How SMS Sending Numbers Work Inside Automations
How to Add A2P 10DLC Language to an Automation
How to Prevent Multiple Automations from Running on the Same Lead