Regenerate a Stale Campaign Plan

Overview

A campaign plan is generated from a strategy snapshot—objectives, key messages, funnel mix, content types, channel frequencies, destinations, and date bounds frozen at generation time. When you materially edit the communication strategy, add or replace source documents, change campaign dates, or adjust targets and child strategy channels, CntX may mark the existing plan as stale. Stale does not mean broken; it means the live strategy contract no longer matches what produced the current slots and briefs.

Continuing to approve stale briefs risks publishing off-message content: wrong dates, retired key messages, channels you disabled, or volumes that no longer fit the shortened launch window. Regeneration rebuilds the plan skeleton and brief set through the same durable orchestration used in initial generation—sequential by week and workspace, with editorial memory, anti-collision, and targeted repairs—so you get a coherent replacement rather than patchwork edits across hundreds of rows.

Regeneration is destructive to unapproved provisional work depending on policy: briefs still in review may be replaced; approved or in-production briefs may be protected and reconciled rather than silently deleted. Treat regeneration as a deliberate operator action after strategy sign-off, not a button to click on every typo fix.

When to use

Regenerate a stale campaign plan when:

• Campaign detail or plan panel shows a stale or out of date indicator after strategy edits.
• Key messages, objectives, or campaign end date changed post-generation.
• You uploaded new source documents that should reshape angles for the whole window.
• You added or removed a target workspace or materially changed child strategy channels.
• Initial generation ran with incomplete strategy bootstrap and you finished configuration afterward.
• Review surfaced systematic issues—wrong funnel mix, repeated angles immune to manual fixes—better solved by a fresh plan.

Prefer individual brief edit or remove for one-off fixes on an otherwise valid plan. Regenerate when problems are systemic.

Before you start

• Finish Generate and Edit a Campaign Strategy edits and save all tabs (Common plus each workspace).
• Confirm source documents are indexed if regeneration should use new retrieval content.
• Inventory approved or in-production briefs you must keep—note dates and titles before regenerating so you can reconcile if the UI prompts about protected items.
• Align stakeholders that review queues may reset for unapproved briefs.
• Check capacity on critical weeks if evergreen calendars also changed during the stale period.

Steps

1. Open Campaigns → [campaign name] and locate the plan panel, progress step, or stale banner on campaign detail.
2. Read the stale reason when shown—common triggers include strategy fingerprint change, document hash change, or date range shift.
3. Open Strategy and verify the current common and workspace tabs reflect sign-off. Undo accidental edits if stale flag appeared from experimental tweaks.
4. Return to campaign detail and choose Regenerate plan, Refresh plan, or equivalent action. Confirm warnings about replacing provisional briefs.
5. Wait for durable orchestration to complete. Progress mirrors initial generation: weeks in chronological order, workspaces in stable order, cumulative memory applied across the run.
6. When finished, open the Briefs table with filters cleared. Compare counts and date span to the campaign window—ensure end weeks are not empty unless you shortened dates intentionally.
7. Re-run Quick Review from the top. Do not assume previously approved brief IDs still exist; re-validate priorities.
8. Cross-check one Calendar per target workspace on launch week and mid-campaign week for date alignment and campaign layer visibility.
9. Remove any orphaned duplicates if reconciliation left edge cases—rare when protected brief logic applies; filter by title similarity on the same date.
10. Resume normal Review, Approve and Remove Campaign Briefs workflow until the refreshed set is production-ready.

Expected result

A new CampaignPlan generation pass aligned with the current strategy snapshot and document index. Stale indicators clear when fingerprint and plan version match. Briefs in review reflect updated key messages, channels, and dates; protected approved briefs remain where reconciliation policy preserves them.

Editorial memory from the new run avoids repeating mistakes from the previous generation while still diversifying angles under new messaging. Capacity assessments recalculate against current reservations and evergreen calendar items.

Tips / common issues

• Regenerate immediately after tiny edit — Strategy fingerprint may flag stale on minor saves. Batch meaningful edits before regenerating to avoid review thrash.
• Lost approved work — Check protection rules: approved or in-production briefs should survive or prompt explicitly. If unsure, export or screenshot approved titles before regenerating large campaigns.
• Same problems after regen — Strategy root cause unchanged—weak pillars, too many enabled channels, missing documents. Fix strategy and documents first.
• Partial weeks empty — End date shortened or channel frequencies lowered to zero on a child tab. Inspect workspace diffusion settings.
• Long runtime — Expected for multi-target campaigns; durable runs resume on failure better than legacy monolithic jobs, but still require patience.
• Stale flag persists — Save all strategy tabs, ensure document processing completed, refresh campaign detail. If flag remains, strategy and plan fingerprints may still diverge—contact support with campaign ID.
• Evergreen calendar unchanged — Regeneration affects campaign slots; it does not rebuild unrelated content strategies. Switch calendar focus strategy explicitly for evergreen regen.

Next step

Review, Approve and Remove Campaign Briefs to validate the refreshed brief set before sending work to production.