Repository navigation
Fix TigerInbox connector getting stuck after an auth failure - #27
Merged
Merged
Conversation
…fingerprint A connection whose token was once rejected stayed in the agents SDK's 'failed' (or OAuth 'authenticating') state for the life of the Durable Object, so the connector kept failing even after the secret was corrected. Bearer-token apps now reconnect fresh when their stored connection is failed or authenticating.
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.
Why PI couldn't use TigerInbox: its requests were rejected with 401, after which the MCP client looked for OAuth metadata, received TigerInbox's HTML login page (fixed in TigerMail) and marked the connection failed; the agents SDK then kept that failed connection for the life of the Durable Object, so every chat failed the same way.
failed/authenticatingstate are dropped and reconnected freshTIGERINBOX_MCP_TOKENWorker secret was re-set via wrangler to TigerInbox's current token (fingerprint3ca538f737f4, matching TigerInbox's running container)Report: https://claude.ai/artifact/TqvjE2bPrGsvxnp6ixqxMy