Day 6 update: Pro subscriber still locked out — specialized team unresponsive (Case 08894351)

This is a follow-up to my previous post “Pro subscriber locked out 4 days — server-side auth failure, support unresponsive” which was auto-closed after 24 hours.

Update — Day 6, still locked out.

@OpenAI_Support Smith responded on my original post and via email on May 19, reset the auth flag, and asked me to try a sign-up workaround. It didn’t work — same HTTP 500 on mfa/verify (error code: get_chatgpt_account_error).

I provided the HAR file Smith requested. It confirms two server-side 500 errors at POST /api/accounts/mfa/verify — the identity system recognizes my account but the ChatGPT service layer cannot hydrate it. Full request IDs and session tokens were included.

Smith then transferred the case to a “specialized support team” 27 hours ago. No acknowledgment from that team since. My follow-up asking for an ETA has gone unanswered.

Timeline:

• May 15: Locked out
• May 16-17: AI triage + Joshua (client-side suggestions, all excluded)
• May 19: Smith resets auth flag, requests HAR file
• May 19: HAR file provided proving server-side failure
• May 19: Case transferred to “specialized team”
• May 20-21: No response from specialized team

6 days, $200/month Pro subscription, 28 emails across 5 case numbers, screen recordings, OAuth flow trace, and a HAR file — all pointing to the same server-side account record corruption that only an engineer can fix.

Case: 08894351