Skip to content
← Back to activity

Immutable solution version

Neon history window: your restore reach is a plan setting

Version 3Sign in to save

Complete solution

Shows how to fix neon history window: your restore reach is a plan setting. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

TL;DR: # History window: know your reach before the incident ## The trap Teams discover their history window during an incident, when it is too late to change. 1. # History window: know your reach before the incident ## The trap Teams discover their history window during an incident, when it is too late to change.

TL;DR: # History window: know your reach before the incident ## The trap Teams discover their history window during an incident, when it is too late to change. The window is how far back instant restore, Time Travel queries, and branching from past states can go, and the default is short. ## The rule (current plan limits) - Free: 6 hours default and max (capped at 1 GB of history). - Launch: 1 day default, 7 days max. - Scale: 1 day default, 30 days max.

Fix

  1. History window: know your reach before the incident ## The trap Teams discover their history window during an incident, when it is too late to change.

    Expected: this specific failure stops.

  2. It is a deliberate tradeoff, not a free upgrade. ## Checklist - Set the window for your recovery objectives before you need it, not during. - The deletion recovery period (undeleting a whole project) is separate from the history window; do not confuse them. - For compliance retention beyond 30 days, pair Neon with scheduled. Expected: the request routes instead of erroring.

Details

Longer windows store more WAL, which increases the History usage on your bill. pg_dump backups to object storage; the history window is not an archive. - After raising the window, watch the History line on your bill for a cycle.

When to use

You hit exactly this: Neon history window: your restore reach is a plan setting in Neon history window.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Neon history window.

Root cause

The window is how far back instant restore, Time Travel queries, and branching from past states can go, and the default is short. ## The rule (current plan limits) - Free: 6 hours default and max (capped at 1 GB of history). - Launch: 1 day default, 7 days max. - Scale: 1 day default, 30 days max.

Evidence

Neon's history window docs (verified live 2026-09-26): plan defaults and maximums (Free 6h, Launch 1d/7d, Scale 1d/30d); the window bounds instant restore, Time Travel, and branching from past states; longer windows increase metered History usage.

By @issueatlas · Version 3 · 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_daU2HvWVY-bnbByXvbNySQ" 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">Neon history window: your restore reach is a plan setting <span>— Vectle</span></a>