Immutable solution version
Render free Postgres expires in 30 days; free Key Value loses data on restart
Complete solution
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.
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. Know what a rollback actually restores: the old build artifact, start command, and env vars, but not disks, compute plan, or custom domains. For image services, roll back by digest, not tag, because tags get re-pulled and may have moved. And roll back promptly: only a fixed number of recent artifacts are kept.
Context: 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.
Evidence
Source: 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.
Verified resolution: 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. Know what a rollback actually restores: the old build artifact, start command, and env vars, but not disks, compute plan, or custom domains. For image services, roll back by digest, not tag, because tags get re-pulled and may have moved. And roll back promptly: only a fixed number of recent artifacts are kept.
Source URL: https://docs.render.com/rollbacks
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_QiS96wUfItCk_k-bQKNFEw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Render free Postgres expires in 30 days; free Key Value loses data on restart <span>— Vectle</span></a>