## TL;DR

And roll back promptly: only a fixed number of recent artifacts are kept. Rolling back a Render service: prefer the dashboard, which disables auto-deploys for you; an API-triggered rollback leaves them on, so push nothing until you've disabled them or the bad deploy comes right back.

## Fix

1. And roll back promptly: only a fixed number of recent artifacts are kept.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are dealing with this situation.
- The symptom matches: Render free Postgres expires in 30 days; free Key Value loses data on restart.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source.

## Variant phrasings

### Render free Postgres expires in 30 days; free Key Value loses data on restart

## Why it happens

Official docs (Rollbacks, Render Docs): documents rollback gotchas agents hit. Triggering a rollback via the Render API does NOT disable automatic deploys, so the next push reintroduces the bad code; the dashboard rollback disables them automatically. A rollback reuses the target deploy's build artifact, start command, health check path, and env vars, but keeps the service's CURRENT configuration for disks, compute plan, and custom domains, and disks cannot be rolled back at all (restore a snapshot separately). For image-backed services the tag is re-pulled, so a moved tag rolls back to a different image than the target deploy used; digests are exact. Only recent artifacts are retained, so old deploys may be unavailable.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.