Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix ChatGPT Data Controls export loops through MFA without creating export request [1 comments, 2 participants]

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…
GitHub stats
openai/codex#20999•Fetched 2026-05-05 05:54:45
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
EARTHTOEDWARDEARTHTOEDWARD
Participants
EARTHTOEDWARDEARTHTOEDWARDetraut-openaietraut-openai
Timeline (top)
labeled ×2commented ×1

ChatGPT web Data Controls export appears to loop through MFA without creating a data export request.

After clicking Export -> Confirm export, ChatGPT redirects to OpenAI identity verification. The email OTP is accepted and the user is returned to ChatGPT Data Controls, but no success state appears and the Export button remains available. Retrying Export -> Confirm export immediately triggers MFA again.

This has reportedly persisted for several days.

Error Message

  • show a specific actionable error explaining why the export was not created.

Root Cause

ChatGPT web Data Controls export appears to loop through MFA without creating a data export request.

After clicking Export -> Confirm export, ChatGPT redirects to OpenAI identity verification. The email OTP is accepted and the user is returned to ChatGPT Data Controls, but no success state appears and the Export button remains available. Retrying Export -> Confirm export immediately triggers MFA again.

This has reportedly persisted for several days.

RAW_BUFFERClick to expand / collapse

Summary

ChatGPT web Data Controls export appears to loop through MFA without creating a data export request.

After clicking Export -> Confirm export, ChatGPT redirects to OpenAI identity verification. The email OTP is accepted and the user is returned to ChatGPT Data Controls, but no success state appears and the Export button remains available. Retrying Export -> Confirm export immediately triggers MFA again.

This has reportedly persisted for several days.

Product area

  • Product: ChatGPT web
  • Surface: Settings -> Data Controls -> Export data
  • Auth surface: OpenAI MFA / email OTP
  • Account type: ChatGPT Pro
  • Observed through: Codex in-app browser controlling ChatGPT web

Steps observed

  1. Open ChatGPT web while signed in.
  2. Open Settings -> Data Controls.
  3. Click Export in the Export data row.
  4. Click Confirm export.
  5. Complete email OTP verification.
  6. Browser returns to ChatGPT Data Controls.

Expected behavior

After successful MFA, ChatGPT should either:

  • create the export request and show a clear confirmation that the export email will arrive, or
  • show a specific actionable error explaining why the export was not created.

Actual behavior

The browser returns to Data Controls with the Export button still present and no visible confirmation. Retrying the export immediately triggers MFA again.

Console signals observed

These may or may not be causal:

  • Uncaught (in promise) from a ChatGPT CDN asset.
  • A router only supports one blocker at a time warnings from ChatGPT CDN assets.
  • Datadog Browser SDK customer-data-size warnings on auth pages.

Impact

The user cannot obtain an official ChatGPT data export for local archival and private ingestion. This blocks workflows that intentionally avoid scraping ChatGPT pages and depend on the official export zip.

Privacy note

This report intentionally excludes OTP values, account email, raw export contents, private conversation URLs, and MFA challenge IDs.

extent analysis

TL;DR

The issue may be resolved by investigating and addressing the Uncaught (in promise) error from the ChatGPT CDN asset, which could be preventing the export request from being created after MFA verification.

Guidance

  • Investigate the Uncaught (in promise) error from the ChatGPT CDN asset to determine its cause and potential impact on the export request creation process.
  • Verify that the MFA verification process is completing successfully and that the user is being redirected back to the ChatGPT Data Controls page as expected.
  • Check the browser console for any other errors or warnings that may be related to the issue, such as the A router only supports one blocker at a time warnings.
  • Consider testing the export process in a different browser or environment to determine if the issue is specific to the current setup.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue may be related to a technical problem with the ChatGPT web application or the MFA verification process, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and address the Uncaught (in promise) error, as it is the most likely cause of the issue and resolving it may allow the export request to be created successfully.

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…

FAQ

Expected behavior

After successful MFA, ChatGPT should either:

  • create the export request and show a clear confirmation that the export email will arrive, or
  • show a specific actionable error explaining why the export was not created.
#api#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix ChatGPT Data Controls export loops through MFA without creating export request [1 comments, 2 participants]