Reasons Why Your Campaign Steps May Be Skipped
Last updated: September 23, 2026
If you notice that some steps in your campaign are being skipped, it’s usually not a bug; it’s the system working as designed. There are several valid reasons this can happen, and most of the time, it simply means Buzz is avoiding redundant or unnecessary actions. It's important to note that steps are skipped on a prospect-by-prospect basis, not campaign-wide. When a step is skipped for one prospect, it doesn't mean it will be skipped for all prospects in the campaign—each prospect's circumstances are evaluated individually.
Here’s a breakdown of why steps might be skipped and how to check if your campaign is still on track:
1. The Task Type Is Obsolete and Can Be Skipped (Currently Applies to Voicemail)
Some task types, like voicemail, aren’t supported or relevant in the current campaign setup. When Buzz identifies such tasks, it automatically skips them to keep your campaign efficient. You don’t need to take any action here. Just know that outdated steps like voicemail are intentionally ignored.
2. You Resume the Prospect, Skipping Several Steps
It means that the user manually skipped the step or resumed the campaign for the prospect in a way that bypasses multiple steps. Resuming after skipping several steps is only possible for Simple campaigns.
3. The Message to Be Sent Already Exists
Buzz checks for duplicate messages. If the message planned for that step has already been sent to the prospect (either manually or by automation), the platform will skip the step to avoid repetition and potential spammy behavior.
4. The Profile Was Connected Before the Task Was Executed
If a campaign step involves sending a connection request, but the prospect has already accepted a previous one, Buzz will skip that connection request. There's no need to connect again, and the platform moves on to the next logical step. For example, a "Send Connection Request" step will be skipped for prospects you are already connected with, but will be successfully executed for prospects you aren't connected to.
Timing Considerations for “If Connected” Steps
If prospects appear stuck at an “If Connected” conditional step even though they are connected, the check may have run before the connection was fully accepted and registered in the system. In that case, Buzz does not detect the established connection, so the prospect may not proceed to the next step as expected.
To resolve this, increase the delay before the “If Connected” step in your campaign. This gives the platform more time to register the accepted connection before performing the conditional check.
5. A Connection Request Had Already Been Sent
If the system detects that a connection request is already pending, it won’t send another, since the Social Platform only allows one request per person at a time.
6. A Connection Request Was Previously Withdrawn
If you previously sent a connection request to a prospect and then withdrew it yourself (not removed by the prospect), LinkedIn requires a mandatory waiting period before you can send another request to the same profile. Specifically, LinkedIn enforces a 3-week waiting period from when the connection was withdrawn.
If a connection request was previously withdrawn for a prospect—either manually or automatically after remaining unanswered—the Social Platform's policies prevent sending a new connection request to the same person until at least three weeks have passed. When Buzz encounters prospects in this state at a "Send Connection Request" step, it will skip the step to comply with platform restrictions. During this waiting period, the campaign may appear inactive for that prospect, but the system will automatically retry once the three-week period has elapsed.
7. The Profile Was Already Enriched
If a campaign step involves enriching a profile with data, but the profile is already enriched, Buzz will skip this step. The system avoids doing redundant work and keeps things moving forward.
8. An Event Invitation Had Already Been Sent
If your campaign includes steps that invite a prospect to an event, and that invite has already been sent (whether through Buzz or another method), it won’t be sent again. This helps avoid confusing your prospect with multiple identical invites.
9. An InMail Had Already Been Sent
If the campaign includes sending an InMail and one has already been sent to the prospect, Buzz skips the step.
10. The Next Step Had Already Been Completed (e.g., After Changing Step Order)
If you edit your campaign and change the order of steps after it’s already started, Buzz checks whether any of the new “next” steps have already been completed. If they have, the platform skips them to avoid duplicating actions or messages.
Important: When you move messages or change the campaign sequence, prospects who have already been contacted may be automatically paused. To resume your campaign for these prospects, you'll need to activate them in bulk from the contacted folder. Without this reactivation, these prospects won't receive subsequent messages in your updated sequence.
If steps are being skipped, it’s usually a sign that the system is working smartly, not that something’s broken. To confirm whether everything is still on track, review your campaign timeline and prospect activity. Buzz ensures your outreach stays relevant, efficient, and free from duplication.
Viewing Skipped Steps
There is currently no bulk view to see which prospects had skipped steps across your campaign. Skipped step indicators do not appear in the main Prospects list view.
To see if a step was skipped for a specific prospect and understand why:
Open the prospect card for the individual prospect
Check the campaign steps section—if a step was skipped, the system will display "skipped" near the step's name along with the reason
Alternatively, view the prospect's info card → Tasks to see underlying subtasks and their status
Keep in mind that in many cases, a skipped step is expected behavior for a prospect and does not indicate an error.
If you have any other questions regarding tasks or the way they are performed, please don’t hesitate to contact our Customer Support team.