- purchase diagnostics show unexpected failures
- the treatment has a support or refund signal
- an app release changed the tested surface
- traffic quality changed during the run
- you need to inspect variant-level results before continuing
What pause should mean
Pausing moves a running experiment out of active assignment while preserving historical assignments and analysis context. AppActor invalidates experiment caches when status changes so future SDK reads can reflect the new state. Your app should continue to handle cached or previously fetched assignment state safely. If the SDK cannot return an active assignment, it should fall back to the app’s default behavior or a stable Remote Config value.After the pause
Decide whether to:- resume with the same traffic split
- change traffic and continue
- stop the experiment
- roll back to the default Remote Config
- move the experiment back to draft if the setup needs a larger correction