You scheduled a bulk pause or resume and it didn't do what you expected — it didn't run, or it ran but skipped people. Here's how scheduled actions work and what to check.
What's happening
Scheduled actions are future membership changes — a bulk pause, a bulk resume, or a single-membership pause — that fire automatically on the date you set. They don't run the moment you create them, and there's no "run now" button: the system executes them on the scheduled date.
Before that, the action carries a Preflight Result — a preview of which targets are eligible and which would be skipped, with the reasons. A target is typically skipped because it's already in the state you're asking for (for example, already paused) or doesn't match the filter on the run date.
The tabs across the list reflect the lifecycle: Pending → Running → Completed (or Partial, Failed, Cancelled).
How to fix it
- Open Scheduled Actions. Use the tabs to find your action — start with Pending if it hasn't run yet, or Completed / Partial / Failed if it should have.
- Check the summary cards: Next scheduled date tells you when the earliest pending action will fire, and Needs follow-up counts actions with failures or pre-run blocks.
- Open the action (the eye / View details). Read What staff should know — it states plainly whether anything is needed.
- If it's still Pending: look at the Preflight Result — eligible vs skipped, with Skipped reasons. If the numbers look stale (memberships changed since you scheduled it), select Refresh to re-run the preview. The action will still fire on its scheduled date; nothing to do unless the preflight shows everyone blocked.
- If it ran (Completed / Partial / Failed): open the Execution Result — Succeeded, Failed, Skipped. Failed and skipped targets are explained in the follow-up text. Resolve those memberships individually, or schedule a narrower action for the ones that need it.
- If it shows Cancelled: someone cancelled it before it ran. Re-create it with Schedule New if it's still needed.
If a Pending action's scheduled date has clearly passed and it never moved to a run state, contact support with the action's scheduled date and type so the run can be investigated.