docs(gotchas): planLimitReached is masked by the cold-start message (FT-5227)#104
Merged
Merged
Conversation
…FT-5227) Hit while re-proving the streams module: every database in the workspace refused connections, but the first connect reported the FT-5226 cold-start "not configured correctly yet — try again in a minute or two" message. Only a warm retry revealed the real cause, a permanent account restriction. The two conditions want opposite responses (retry vs stop and reclaim), and a bounded cold-start retry spends its whole budget re-showing the misleading one. Through the hosted state store it surfaces as an ownership-verification failure, pointing at the state store rather than the account. Records the disambiguating probe: a freshly created database connects on the first attempt while the existing ones keep failing. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
wmadden
approved these changes
Jul 16, 2026
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.
Intent
Record a Prisma Postgres gotcha hit while re-proving the streams module (#92): every database in the workspace refused connections, but the first connect returned the FT-5226 cold-start message — "not configured correctly yet… try again in a minute or two" — while the real cause, a permanent
Your account has restrictions: planLimitReached, only appeared on a warm retry. The two conditions want opposite responses (retry vs. stop and reclaim a database), so the message that arrives first tells you to do the wrong thing, and the documented cold-start retry spends its whole budget re-showing it. Through our hosted state store it surfaces as an ownership-verification failure, pointing a layer away from the cause.The entry also records the disambiguating probe: a freshly created database connects on the first attempt while the existing ones keep failing, which identifies a count limit rather than a broken database or a cold proxy.
Upstream ticket: FT-5227.
Scope
gotchas.mdonly — one new entry plus its contents-table line, following the existing entry format.Deliberately not included: the sibling finding that a failed state bootstrap orphans a project + database is our own framework's behaviour, and this file is scoped to friction hit while consuming Prisma Next / Compute / Postgres. It is filed as #103 instead.
Verification
Docs-only change; no code paths affected. Cross-references FT-5226 (the message this is confused with) and
state/bootstrap.ts'sverifyOwnership, where it surfaced.🤖 Generated with Claude Code