Repository navigation
Explain unsupported Global service scaling without plan retries - #231
Merged
Merged
Conversation
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.
An authoritative
422 ResourceChangeUnsupportedalready rejects the tool call,but its next step incorrectly suggested enabling the integration. The reply now
explains that Global services follow eligible hosts and cannot accept a manual
instance count; it directs callers to review deployment configuration instead
of retrying a plan or guessing counts.
The change is restricted to that exact response. Permission, stale snapshot,
feature-off and uncertain transport categories remain unchanged. No new UI
translation keys, Catalog adapter or archive changes are included.
Three focused error-boundary cases, the actual SDK version handshake and the
version gate passed. Web Console is 1.6.199 and bridge 0.2.1; dependencies and
links are unchanged. Required CI/CodeQL and immutable artifact checks remain
gates; new Server/browser acceptance is separate. Existing 1.6.198/0.2.0 assets
remain immutable.