What is the retention period for source maps?

I want to understand how long Sentry keeps uploaded source maps and related artifacts, including Debug IDs, and what causes them to expire.

Sentry retains uploaded source map artifacts, including Debug ID-based uploads, using a 90-day time-to-idle retention policy.

An artifact stays available as long as Sentry continues to use it to process incoming events, such as when it’s needed to turn a minified stack trace into readable source code. If an artifact hasn’t been used to process an event for 90 consecutive days, it expires and becomes eligible for deletion.

Activity that requires the artifact, such as a new error event that needs it for processing, resets the 90-day idle period. Re-uploading the artifact also resets the retention period.

This retention policy is separate from event retention. How long Sentry stores your error events depends on your plan. For more information, see How Long Are Errors/Events Stored in Sentry?.

You can find more details about this policy in the Debug IDs retention policy. The same time-to-idle model applies to debug files.