Description
Ensure production Key Value instances used for job queues, sessions, or other data that must not be lost have their Persistence Mode set to Journal + Snapshot (or at least Snapshot only), so data is saved to disk and survives restarts. Instances used only as caches can keep persistence off.
Rationale
With persistence off, all data is lost whenever the instance restarts, is upgraded, or fails. For queues and sessions, that means lost jobs and logged-out users. Persistence writes data to disk, encrypted at rest with AES-256, so it can be recovered after a restart.
Impact
Queue and session data survives restarts
Reduces data loss during maintenance
Changing the mode restarts the instance, and switching to or from Off clears its data
Default Value
Paid Key Value instances support disk-backed persistence and enable it by default. Free instances do not support persistence.
Pre-Requisites
Admin or Developer role (Admin for protected environments)
A paid Key Value plan
Remediation
Test Plan
Sign in to the Render Dashboard at https://dashboard.render.com.
From your workspace home (or project), click the Key Value instance to open it.
On the Info page, check the Persistence Mode.
If a production instance used for queues or sessions shows Off, or is on the Free plan, follow the implementation steps.
Implementation Steps
Sign in to the Render Dashboard at https://dashboard.render.com.
From your workspace home (or project), click the Key Value instance to open it.
If the instance is on the Free plan, upgrade it from the Key Value Instance section (Compute Plan > Update). Data on Free instances is lost during the upgrade.
Set the Persistence Mode to Journal + Snapshot and save. The instance restarts, and data is cleared when switching from Off.
Backout Plan
Sign in to the Render Dashboard at https://dashboard.render.com.
From your workspace home (or project), click the Key Value instance to open it.
Set the Persistence Mode back to its previous value and save.
Reference