Pausing a campaign in AI Content Generator is a one-click operation, but doing it wrong deletes your queued schedule — cron events, upcoming generations, catch-up state, everything. Doing it right freezes all of that in place so a Resume click brings the campaign back exactly where you left it. This tutorial covers the correct pause/resume workflow, when to use it, the difference between pause and deactivate, and the common recovery scenarios.
Where the Pause and Resume buttons live
Inside any campaign editor, the right-sidebar Generation & controls metabox has two buttons below the big blue “Generate content for selected titles” button: Pause and Resume. The active one is highlighted; the other is greyed out based on the campaign’s current state.
Click Pause on a running campaign and three things happen: the next scheduled generation is cancelled, the Article log stops recording new events, and the campaign status badge (visible at the top of the editor) changes to “Paused”. Nothing else — the campaign’s Base data, titles queue, categories, provider, everything else stays exactly as configured.
Pause vs deactivate: know the difference
Deactivating a campaign (setting its Publish status to Draft/Trash from the top-of-editor Publish metabox) is a bigger operation than pausing. Deactivation removes the campaign from the cron queue entirely, disables Live News Mode polling, and detaches the campaign from its schedule. Reactivating means rebuilding all of that.
Pause is lighter: everything stays wired up, only the “keep generating” flag flips off. For a two-week vacation, always Pause — not deactivate.
When to pause
- Editorial holidays — Christmas week, Easter week, summer break. Pause on the day the holiday starts, resume on the return day.
- Major site event — you’re publishing a big announcement, don’t want the auto-cron flooding the front page around it.
- AI provider outage — OpenAI or Claude is having an incident. Pause instead of accumulating failed generations in the Error log.
- Editorial rework — you’re changing tone or restructuring categories. Pause, edit, resume.
Step 1 — Pause the campaign
Open the campaign editor. In the Generation & controls metabox, click Pause. The button greys out; the Resume button becomes active. The campaign status changes to Paused within a second.
Any generation currently in-flight completes normally — Pause doesn’t kill running work, it just prevents new work from starting. The last generation finishes, the article ends up in Drafts, then the campaign quiets down.
Step 2 — Verify pause on the Content calendar
Open the Content calendar. Filter by the paused campaign. You’ll see the previously scheduled slots for future days grey out — the schedule is remembered, just deferred. When you resume, they’ll reactivate.
This visual confirmation matters because it tells you the pause was clean. If slots don’t grey out, something went wrong — refresh the page and check the campaign state.
Step 3 — Resume the campaign
When you’re ready to restart, open the campaign editor and click Resume. The campaign status returns to Active. The next scheduled generation slot activates within the interval configured in Base data.
If the “Catch up missed articles after pause” checkbox in Base data is ticked, the plugin also queues catch-up generations for the slots you missed during the pause. If unchecked, missed slots are simply lost.
Common patterns
- Quick pause during a big announcement — pause 1 hour before, resume 6 hours after. Catch up disabled to avoid flooding.
- Two-week vacation — pause the day you leave, resume the day you return. Catch up enabled for cornerstone campaigns; disabled for news.
- Multi-campaign pause — pause each campaign individually. There’s no bulk pause; that’s on purpose, so you can leave one running while pausing others.
What happens to Live News Mode during pause
Live News Mode polling stops when the campaign is paused. New RSS/NewsAPI/Tavily items aren’t fetched. When you resume, polling restarts on the next interval — but items published during the pause are lost (they’re older than the News search window by then).
For news campaigns this is usually the right behaviour: stale news isn’t news. If you must cover events from the pause period, temporarily widen the News search window on resume.
Troubleshooting
- Pause button doesn’t respond — page cached. Refresh with cmd/ctrl+shift+R.
- Campaign resumes but doesn’t generate anything — title queue is empty. Add titles.
- Catch-up floods the queue after resume — Catch up was enabled and pause was longer than intended. Disable Catch up and manually queue the articles you actually want.
- Cron doesn’t fire after resume — WP-Cron itself is stalled. See the external cron tutorial.
- Calendar shows Paused slots as scheduled — page cached. Refresh.
You’re done
That’s the pause/resume workflow: click Pause to freeze, click Resume to restart, know the difference vs deactivate, mind the Catch up interaction on long pauses. The editorial calendar handles vacations, announcements and outages without losing scheduling state.