docs(ai): document snapshot per-hour scheduling limit (blocked on neon-cloud#9065) - #5559
Open
bgrenon wants to merge 6 commits into
Open
docs(ai): document snapshot per-hour scheduling limit (blocked on neon-cloud#9065)#5559bgrenon wants to merge 6 commits into
bgrenon wants to merge 6 commits into
Conversation
Add a "Scheduling snapshots at scale" section to the AI database-versioning guide, documenting the per-account 5,000-scheduled-snapshots-per-hour limit and how high-volume/agent-platform builders should distribute the schedule hour to stay under it. Tracking: DOC-25882. Co-authored-by: Isaac
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
added 2 commits
August 17, 2026 13:36
Rework the 'Scheduling snapshots at scale' section into concise prose: drop the admonition callout and the verbatim (still-TBD) error string, inline the hash/cycle/random strategies, and keep the per-account 5,000 snapshots-per-hour default limit and hour-distribution guidance. Tracking: DOC-25882. Co-authored-by: Isaac
Apply the approved final wording for the 'Scheduling snapshots at scale' section: recommend distributing snapshot creation across several hours, state the per-account 5,000 snapshots-per-hour default limit, and keep the hour-distribution strategies (hash/cycle/random). Tracking: DOC-25882. Co-authored-by: Isaac
Present the hour-distribution strategies (hash/cycle/random) as three bold lead-in bullets instead of an inline list. No wording change to the first two paragraphs. Tracking: DOC-25882. Co-authored-by: Isaac
Per Neon eng reviewer feedback, remove the private per-account/per-hour numeric limit and any mechanism/consequence framing. Keep it a bare good-practice recommendation: distribute scheduled snapshot creation across hours (midnight shown only as concentration to avoid), with the hash/cycle/random strategies. Tracking: DOC-25882. Co-authored-by: Isaac
Break the first paragraph of 'Scheduling snapshots at scale' into two sentences; move the midnight illustration into its own 'For example' sentence. No other content changes. Tracking: DOC-25882. Co-authored-by: Isaac
zaynetro
approved these changes
Aug 18, 2026
bgrenon
marked this pull request as ready for review
August 24, 2026 14:13
bgrenon
requested review from
andrelandgraf,
danieltprice,
philip and
ruf-io
as code owners
August 24, 2026 14:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a "Scheduling snapshots at scale" section to the AI database-versioning guide, documenting the per-account 5,000-scheduled-snapshots-per-hour limit and how high-volume/agent-platform builders should distribute the schedule
hourto stay under it.Eng PR: https://github.com/databricks-eng/neon-cloud/pull/9065 (
[cplane/public_api] feat: Hard limit snapshot schedules per account per hour) is currently OPEN / not merged. The limit value (5,000, a live-config default), the error string, and whether it ships at all can still change in review. Hold this docs PR as a draft until #9065 merges, then reconcile the number/error text against the merged code before marking ready.Tracking: DOC-25882.