ChatGPT Data Controls export loops through MFA without creating export request

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.