Scheduled analysis refreshes for monitored ramps

A monitored ramp watches guardrail metrics as it moves through its steps, and its status updates as new results come in. Scheduled refreshes no longer skip a monitored ramp solely because it lacks a separate Safe Rollout rule. The ramp's own monitoring interval now sets when the next analysis attempt is scheduled.

What changed

Before this fix, the scheduled refresh job looked for a classic Safe Rollout rule that a monitored ramp doesn't have. It could skip the ramp, so the ramp kept waiting for fresh analysis. The job now passes that check for monitored ramps, and the rollout's monitoring interval takes precedence over the organization's experiment update schedule.

How a scheduled refresh behaves

• If an analysis is already running, GrowthBook defers the next attempt instead of starting another.
• A missing or archived feature still stops the refresh.
• A refresh is an attempt to update results. It doesn't mean the analysis has completed or that the ramp has advanced, so review results and step progress separately.

Getting started

• In the feature's rule editor, choose Monitored Ramp-up as the release plan, or turn on Monitor this release on a ramp schedule.
• Use Refresh results every to set how often GrowthBook re-analyzes your metrics, then publish the revision to start the schedule.
• After it starts, check the status and progress shown on the rule. The ramp schedules guide covers monitored steps and guardrails.