[PLT-3072] docs: explain connected account lifecycle recovery - #1154
Open
TheMostlyGreat wants to merge 5 commits into
Open
[PLT-3072] docs: explain connected account lifecycle recovery#1154TheMostlyGreat wants to merge 5 commits into
TheMostlyGreat wants to merge 5 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
TheMostlyGreat
force-pushed
the
codex/unified-eventing-guide
branch
from
August 29, 2026 15:02
ebe76a5 to
558d09b
Compare
TheMostlyGreat
force-pushed
the
codex/connected-account-expiry-docs
branch
from
August 31, 2026 05:07
d5f2bd1 to
ddc3363
Compare
TheMostlyGreat
marked this pull request as ready for review
August 31, 2026 05:07
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.
Why
When a connected account expires, operators need to understand the lifecycle event and reconnect the existing account without recreating triggers.
What
connected_account.created,connected_account.expired, andconnected_account.reconnectedVerification
/en/build/eventingrendered successfullyMerge gate
Ready for review as a child of #1146. Merge and publication remain intentionally gated on the parent guide and corresponding Engine release.
Linear: https://linear.app/arcadedev/issue/PLT-3072
Note
Low Risk
Documentation and contract tests only; no runtime, auth, or data-path changes.
Overview
Adds a Recover expired connected accounts section to the unified eventing guide, placed before the scheduled-event walkthrough.
The new content covers subscribing to
connected_account.created,connected_account.expired, andconnected_account.reconnected; verifying Standard Webhooks signatures; the expired-event payload andno_refresh_token/refresh_failedreasons; project-scoped subscriptions vs organization-bound connections (noproject_id); and recovery via Dashboard Reconnect orPOST .../auth/authorize, including scope behavior and trigger health afterconnected_account.reconnected. It also states that MCP-managed OAuth does not emit these lifecycle events or use the standard reconnect path.tests/eventing-guide.test.ts gains a section-scoped test that asserts those strings, API paths, and the documented JSON envelope field set.
Reviewed by Cursor Bugbot for commit ddc3363. Bugbot is set up for automated code reviews on this repo. Configure here.