auth: dedicated page for health checks and re-auth#365
Draft
dprevoznik wants to merge 2 commits into
Draft
Conversation
Consolidates scattered FAQ entries on health check cadence, can_reauth eligibility, manual re-auth, login failure codes, and debugging into a single Health Checks & Re-Auth page. FAQ entries now defer to the new page with a short summary and link. Overview links to it from the Session monitoring bullet.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk assessment: Very Low
This PR only changes documentation content and Mintlify navigation: it adds auth/health-checks.mdx, moves existing FAQ detail into that dedicated page, updates one overview link, and adds the page to docs.json. I found no production code, infrastructure, auth logic, permissions, or prompt/model-instruction changes in the diff. No CODEOWNERS file was present, and the PR had no existing approvals in the metadata I checked.
Sent by Cursor Automation: Assign PR reviewers
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
1 participant
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
There's no single home for managed auth connection health checks / re-auth troubleshooting today — the content is scattered across the FAQ and lightly touched in Configuration. This adds a dedicated Health Checks & Re-Auth page under Auth.
The new page consolidates:
NEEDS_AUTH)health_check_intervalcan_reautheligibility rules and what blocks auto-reauth.login()credentials_invalid,bot_detected,captcha_blocked,unsupported_auth_method) and how to recover from eachrecord_sessionFAQ entries that were the de-facto reference for this material are trimmed to a one-liner that links into the new page, so the FAQ stays focused on Q&A and the deep content has a stable URL. Overview's "Session monitoring" bullet also links to the new page.
Test plan
#when-a-login-fails,#triggering-re-auth-manually,#debugging-a-flaky-connection)/auth/configuration#custom-proxy,/auth/credentials,/integrations/1password,/browsers/replays,/browsers/bot-detection/overviewall resolve