Repository navigation
docs: describe the install-time 503 and save-before-run - #1120
Merged
Merged
Conversation
Helm: while the post-install bootstrap job applies migrations on a bundled install, pods can be Ready while the install is unfinished. In releases after v1.58.0 the API answers 503 "The platform is still initializing; retry shortly." with Retry-After: 5 until the migrations are applied, and logs startup_schema_pending. Say so in the install step and add a troubleshooting row. Prompt: Run Prompt now waits for a just-made change to save, and says "The prompt changed while saving. Run it again." when the compared versions change during that wait. Note both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
This brings docs.futureagi.com in line with two real-user fixes now merged into
future-agi/future-agidev:503"The platform is still initializing; retry shortly." withRetry-After: 5until the migrations are applied, instead of 500s on missing tables.Changes
self-hosting/helm.mdx, bundled install step: readiness and/health/mean process health, not a finished install. In releases after v1.58.0, API requests (the UI's included) get the retryable503until the migrations are applied.self-hosting/helm.mdx, Troubleshooting: a row for that503. It points to the bootstrap job's logs and the API'sstartup_schema_pendinglog line, and says the API recovers on its own without a restart.prompt/guides/run-a-prompt.mdx: Run waits for a just-made change to save, so it uses what the editor shows.prompt/troubleshooting.mdx: a row for "The prompt changed while saving. Run it again."The configuration reference page is unchanged. It is generated from
deploy/env-reference.toml, which covers keys the compose files read. The chart setsSTARTUP_SCHEMA_GUARD_ENABLEDinternally, and the chart README documents it (updated in #3948).Dependencies
Both companion PRs are already merged into
dev: future-agi/future-agi#3948 (579abc98b0) and future-agi/future-agi#3957 (e5ed4ab0fd). The Helm text says "releases after v1.58.0", because v1.58.0, the latest release, does not include them.Validation
Retry-After: 5, the 5-second recheck and thestartup_schema_pendingevent infutureagi/tfc/schema_readiness.pyandtfc/middleware/schema_readiness.py. The prompt message is inWorkbenchProvider.jsx.503withRetry-After: 5during the roughly 9-minute bootstrap, and normal responses afterwards.AI use: Claude Code (Opus 5.5) wrote this change from the merged code and the recorded test evidence. Human review is still required.
🤖 Generated with Claude Code