Skip to content

docs(spec): reconnect_required docblock names every way the grant stops working #28862

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 1 commit into from
Nov 2, 2026
Merged

docs(spec): reconnect_required docblock names every way the grant stops working #28862

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .changeset/28614-connection-reconnect-required-docblock.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
'@objectstack/spec': patch
---

Clause-②: no
Metadata-protocol: none

`ConnectorConnectionState.status`'s docblock no longer says `reconnect_required` means only that the authorization server refused the grant. It now names every way the grant stops working: the authorization server refused it on refresh, the connection keeps nothing to renew an expired access token with (no refresh token was issued, or no client to refresh with), or the upstream refused the connection's token while an `mcp` instance discovered its tools; `statusReason` says which. Comment only; no behaviour change.
6 changes: 5 additions & 1 deletion packages/spec/src/contracts/automation-service.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1134,7 +1134,11 @@ export interface ConnectorConnectionState {
/**
* `not_connected` — no administrator connected it here yet (the instance
* dispatches nothing for this organization); `connected`; or
* `reconnect_required` — the authorization server refused the grant.
* `reconnect_required` — the grant stopped working: the authorization
* server refused it on refresh, the connection keeps nothing to renew an
* expired access token with (no refresh token was issued, or no client to
* refresh with), or the upstream refused the connection's token while an
* `mcp` instance discovered its tools. `statusReason` says which.
*/
status: 'not_connected' | 'connected' | 'reconnect_required';
/** Why the grant stopped working, when `status` is `reconnect_required`. */
Expand Down
Loading