You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document platform 429 response replacement in Functions - #71
Add a warning beside the Functions Request/Response contract: WP Cloud can replace a handler-generated HTTP 429 JSON response with platform HTML, so applications must not rely on their response body or headers, including Retry-After, surviving.
Link the public WP Cloud HTTP status-code reference. The warning is limited to 429 and does not claim that every 4xx/5xx is replaced or prescribe 409 as a universal rate-limit status.
Verification
Using Bun 1.3.11 and Node 26:
check, validate, and build passed.
audit, verify:routes, and verify:public-safety passed.
verify:prose passed with Vale 3.17.1.
Inspected the built Functions page for the warning, Retry-After caveat, and provider reference.
git diff --check passed.
Documentation only. No runtime or provider settings changed; authored 5xx behavior remains unverified.
Tag @indent to continue the conversation here.
Need help on this PR? Tag @codesmith-bot with what you need.
Deploy preview fails with 'Static deploys cannot upload runtime control paths: "storage/index.html"'. The same failure appears on main, and this PR only edits one paragraph in content/(dynamic)/functions.mdx, so it is unrelated.
Review agents
Select any unchecked box below to run or rerun that agent.
Passed (1)
Indent Review Agent · Docs-only 429 note is accurate, correctly scoped, and passes public-safety; no issues found.
Full results
Indent Review Agent
Summary: Docs-only 429 note is accurate, correctly scoped, and passes public-safety; no issues found.
Required CI passed. The separate Spacefast preview build failed because the publisher rejects storage/index.html, unrelated to this documentation change. That restriction already has a fix in spacefast/monorepo#4033, so no duplicate fix is needed here.
preview/docs/functions-429-response-warning—d85ab8aaDeployedOct 12, 2026 by
spacefast[bot]
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
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
Add a warning beside the Functions Request/Response contract: WP Cloud can replace a handler-generated HTTP 429 JSON response with platform HTML, so applications must not rely on their response body or headers, including
Retry-After, surviving.Link the public WP Cloud HTTP status-code reference. The warning is limited to 429 and does not claim that every 4xx/5xx is replaced or prescribe 409 as a universal rate-limit status.
Verification
Using Bun 1.3.11 and Node 26:
check,validate, andbuildpassed.audit,verify:routes, andverify:public-safetypassed.verify:prosepassed with Vale 3.17.1.Retry-Aftercaveat, and provider reference.git diff --checkpassed.Documentation only. No runtime or provider settings changed; authored 5xx behavior remains unverified.
Tag
@indentto continue the conversation here.Need help on this PR? Tag
@codesmith-botwith what you need.