Merged
Conversation
Contributor
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 1 new, 55 changed, 5 removedBuild ID: e4a11d731e95010431a05f0e URL: https://www.apollographql.com/docs/deploy-preview/e4a11d731e95010431a05f0e ✅ AI Style Review — No Issues FoundThe pull request does not have any style issues. Duration: 2627ms
|
abernix
commented
Mar 11, 2026
Member
Author
abernix
left a comment
abernix
left a comment
There was a problem hiding this comment.
Looks good to me and matches the requirements in the PR description.
aaronArinder
approved these changes
Mar 11, 2026
andywgarcia
added a commit
that referenced
this pull request
Mar 11, 2026
Updates the `experimental_hoist_orphan_errors` documentation to match the final config shape from PR #9007 (v2.10.1 release prep): - Config values now use `{ enabled: true/false }` objects instead of bare booleans (e.g., `all: { enabled: true }` not `all: true`) - `all` and `subgraphs` are not mutually exclusive — per-subgraph settings override `all` - Added "all except one" example showing the override pattern - Fixed backtick-wrapped property name inside YAML code block - Updated default values in shared config and YAML reference Co-Authored-By: Claude Opus 4.6 <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
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.
🐛 Fixes
Enforce feature restrictions for warning-state licenses
The router now enforces license restrictions even when a license is in a warning state. Previously, warning-state licenses could bypass enforcement for restricted features.
If your deployment uses restricted features, the router returns an error instead of continuing to run.
By @aaronArinder in #8768
🧪 Experimental
Add
experimental_hoist_orphan_errorsto control orphan error path assignmentThe GraphQL specification requires that errors include a
pathpointing to the most specific field where the error occurred. When a subgraph returns entity errors without valid paths, the router's default behavior is its closest attempt at spec compliance: it assigns each error to every matching entity path in the response. This is the correct behavior when subgraphs respond correctly.However, when a subgraph returns a large number of entity errors without valid paths — for example, 2000 errors for 2000 expected entities — this causes a multiplicative explosion in the error array that can lead to significant memory pressure and out-of-memory kills. The root cause is the subgraph: a spec-compliant subgraph includes correct paths on its entity errors, and fixing the subgraph is the right long-term solution.
The new
experimental_hoist_orphan_errorsconfiguration provides an important mitigation while you work toward that fix. When enabled, the router assigns each orphaned error to the nearest non-array ancestor path instead of duplicating it across every entity. This trades spec-precise path assignment for substantially reduced error volume in the response — a conscious trade-off, not a strict improvement.To target a specific subgraph:
To target all subgraphs:
To target all subgraphs except one:
Per-subgraph settings override
all. Note that this feature reduces the number of propagated errors but doesn't impose a hard cap — if your subgraph returns an extremely large number of errors, the router still processes all of them.You'll likely know if you need this. Use it sparingly, and enable it only if you're affected and have been advised to do so. The behavior of this option is expected to change in a future release.
For full configuration reference and additional examples, see the
experimental_hoist_orphan_errorsdocumentation.By @aaronArinder in #8998