claude-code - 💡(How to fix) Fix [BUG] Three critical support infrastructure failures blocking user resolution — requires engineering intervention

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

No error messages are generated at any point — which is itself part of the bug. No error shown when conflicting subscriptions are created on the same account No error shown when web subscription is silently ignored No error shown when Fin escalation request is dropped without handoff

Root Cause

Bug 1: Apple subscription sync failure Claude.ai account subscription state does not correctly sync with Apple App Store subscription state. Changes made on one platform are not reflected on the other. No reconciliation layer exists between the two systems, resulting in account state that is inconsistent and unresolvable from either side. Bug 2: Fin escalation routing failure When a user explicitly requests a human agent, Fin generates an acknowledgment but does not execute the handoff. The escalation path exists in the UI but is non-functional. The request is silently dropped — no ticket assignment, no routing, no notification to the user. Bug 3: Infinite AI loop with no human exit The support system has no functional exit to human resolution. Each new support contact restarts the AI loop from zero with no preserved context. A class of issues exists that Fin cannot resolve by design, requires human intervention, but has no working path to reach one. Why this needs engineering, not support: These are not edge cases. They are systematic infrastructure failures. A user following every correct step — requesting escalation, providing documentation, referencing conversation IDs — remains permanently stuck because the escalation mechanism itself is broken.

Code Example

No error messages are generated at any point — which is itself part of the bug.

No error shown when conflicting subscriptions are created on the same account
No error shown when web subscription is silently ignored
No error shown when Fin escalation request is dropped without handoff
No confirmation, ticket number, or routing notification when human agent is requested

The system fails silently at every step. The only observable symptoms are:

Billing page displays: "Pro plan — Subscribed via iOS app" with no trace of web subscription
Fin generates escalation acknowledgment text but no human ever contacts the user
Support messenger does not allow new chat sessions to be initiated for follow-up

Conversation IDs documenting the support loop: 215474492636122 / 215474496149866
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Bug 1: Apple subscription sync failure Claude.ai account subscription state does not correctly sync with Apple App Store subscription state. Changes made on one platform are not reflected on the other. No reconciliation layer exists between the two systems, resulting in account state that is inconsistent and unresolvable from either side. Bug 2: Fin escalation routing failure When a user explicitly requests a human agent, Fin generates an acknowledgment but does not execute the handoff. The escalation path exists in the UI but is non-functional. The request is silently dropped — no ticket assignment, no routing, no notification to the user. Bug 3: Infinite AI loop with no human exit The support system has no functional exit to human resolution. Each new support contact restarts the AI loop from zero with no preserved context. A class of issues exists that Fin cannot resolve by design, requires human intervention, but has no working path to reach one. Why this needs engineering, not support: These are not edge cases. They are systematic infrastructure failures. A user following every correct step — requesting escalation, providing documentation, referencing conversation IDs — remains permanently stuck because the escalation mechanism itself is broken.

What Should Happen?

Apple and web subscription states should sync and both be visible on the account When a user requests human escalation, Fin should execute the handoff — not silently drop it A functional path to human support should exist for issues Fin cannot resolve Account associated with Conversation IDs 215474492636123 / 215474496149866 should be immediately flagged for human review — this user has been trapped by all three bugs simultaneously and has exhausted every available support path

Error Messages/Logs

No error messages are generated at any point — which is itself part of the bug.

No error shown when conflicting subscriptions are created on the same account
No error shown when web subscription is silently ignored
No error shown when Fin escalation request is dropped without handoff
No confirmation, ticket number, or routing notification when human agent is requested

The system fails silently at every step. The only observable symptoms are:

Billing page displays: "Pro plan — Subscribed via iOS app" with no trace of web subscription
Fin generates escalation acknowledgment text but no human ever contacts the user
Support messenger does not allow new chat sessions to be initiated for follow-up

Conversation IDs documenting the support loop: 215474492636122 / 215474496149866

Steps to Reproduce

Create a Claude.ai account Subscribe to a plan via iOS App Store Subscribe to a different plan via Claude.ai web on the same account Observe that web plan is invisible in billing settings Contact support and request human escalation via Fin Observe that escalation acknowledgment is generated but no human follows up Attempt to open a new Fin chat to follow up Observe that no new chat can be initiated — user is permanently stuck in AI loop with no exit

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

N/A

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Three critical support infrastructure failures blocking user resolution — requires engineering intervention