Retrying failed drift detection runs

When a drift detection run fails due to intermittent issues (such as rate limiting or temporary service unavailability), you can retry the run using the retry button available on the failed run.

How retried drift detection runs work

When you retry a failed drift detection run, the retried run will maintain the drift_detection = true attribute, ensuring that any policies conditioned on this attribute will fire as expected. This means notification policies and other drift detection-specific policies will work correctly for retried runs.

When to use the retry feature

The retry feature is particularly useful for:

• Intermittent rate limiting issues with external services

• Temporary network connectivity problems

• Other transient failures that don't indicate configuration issues

By retrying failed drift detection runs, you can ensure your drift detection monitoring and notification workflows continue to function properly without having to wait for the next scheduled drift detection cycle.