Schedule experiment stop
You can now schedule when an experiment or flag stops, not just when it starts. Set a start time, an end time, or both. At the end time, delivery stops, the analysis window freezes, and the experiment moves to Completed (Pending decision).
What it is
Description: You can now schedule when an experiment or flag stops, not just when it starts. Set a start time, an end time, or both. At the end time, delivery stops, the analysis window freezes, and the experiment moves to Completed (Pending decision).
What's included:
• Start and end in one modal — check Start time, End time, or both; a Runs 14 days summary confirms the window before you commit
• Auto-stop at the end time — experiments stop delivering variants, flags turn off
• Analysis window freezes at the scheduled stop, so results don't keep extending past the intended end
• Status moves to Completed (Pending decision) and the active-experiment quota slot is released for the next test
• Owners get notified when a scheduled start or stop fires
• Schedule details in the status pill tooltip — see exactly when it starts and stops
Why: Teams had to stop experiments by hand. Miss the window and variants keep shipping past the planned end — stretching analysis and holding an active-experiment slot. Time-boxed tests now end on schedule.
Where: Experiment or flag page → Start Experiment → Schedule. Once running, use Edit schedule.
Available in EUDC: Yes
When: Now!
Docs: https://amplitude.com/docs/feature-experiment/workflow/experiment-test#schedule-your-experiment