By the end of this tutorial, you’ll know how to pause a lemlist campaign from the campaign list or from inside the campaign, so you can stop sends immediately without changing your sequence setup.
Why this matters
Pausing a campaign is the fastest way to prevent new steps from being sent while you review performance, fix targeting, update copy, or troubleshoot an integration. It helps you stay in control without needing to edit or delete your workflow.
Prerequisites
You have access to the lemlist workspace where the campaign lives.
You can see the campaign in your Campaigns list.
Core lesson — Step-by-step workflow
Phase 1: Pause a campaign from the Campaigns list
Go to Campaigns, find the campaign you want to pause, then click the switch next to its name.
Confirm the campaign is paused: the switch will turn grey. This indicates the campaign won’t send new steps until you turn it back on.
Phase 2: Pause a campaign from inside the campaign
Open the campaign, click the campaign status dropdown in the top bar, then select Pause campaign. Use this method when you’re already reviewing stats or editing the sequence and want to stop sends right away.
Confirm the campaign is paused: the top-bar toggle will turn grey and a confirmation message will appear.
Practical application / real-life example
If you notice a spike in bounces or replies indicating your targeting is off, pause the campaign first to prevent additional sends. Then you can update your lead list or message copy and resume the campaign once everything is ready.
Troubleshooting & pitfalls
Issue: The switch is grey but I still see activity.
Root cause: Some actions may already be in progress or recently triggered.
Fix: Refresh the page, confirm the campaign toggle remains grey, and allow a few minutes for in-flight actions to finish.
Issue: I can’t pause the campaign (toggle doesn’t change).
Root cause: Permission restrictions or a temporary UI/loading issue.
Fix: Reload the page, try pausing from inside the campaign using the top bar status menu, and verify you have the required workspace permissions.


