"Previous response cannot be used for this organization due to Zero Data Retention"

Resolved 💬 11 comments Opened Apr 16, 2025 by OmerRaviv Closed Aug 7, 2025
💡 Likely answer: A maintainer (tibo-openai, collaborator) responded on this thread — see the highlighted reply below.

I am using a OpenAI Enterprise account, and no matter what query I put in, codex fails with the following message:

 OpenAI rejected the request (request ID: req_1a9b278241d22896524af079e9ba9c8c). Error details: Status: 400, Code: unsupported_parameter, Type: invalid_request_error, Message: 400 Previous
    response cannot be used for this organization due to Zero Data Retention.. Please verify your settings and try again.

View original on GitHub ↗

11 Comments

bbrzoska · 1 year ago

same issue here

tibo-openai collaborator · 1 year ago

Currently we don't support ZDR orgs because we need store:true to leverage internal reasoning steps, but as per https://platform.openai.com/docs/guides/your-data#responses-api: "Unlike Chat completions, the Responses API has a 30 day retention period by default, or when the store parameter is set to true."

tibo-openai collaborator · 1 year ago

We should document this in the README for now.

ramgsuri · 1 year ago

How and where to set this parameter, can you help explain.

TerminalGravity · 1 year ago

bump

MaccariTA · 1 year ago

Despite being on the latest version (0.1.2505021246) and the README mentions it does support ZDR, I'm still getting this issue.

I'm mentioning @fouad-openai who made the change in the README.

itsaphel · 1 year ago

I find that you need to also use the --disable-response-storage argument for codex to work with ZDR. With that flag, it seems to work for me.

carjessu-trm · 1 year ago

Even trying this with the --disable-response-storage flag, I can't get this to work.

telliott22 · 1 year ago

my orgnization has ZDR enabled and I was experiencing the same error message, adding --disable-response-storage worked for me

james-hayes-emburse · 12 months ago

Here's the fix that worked for me: add disable_response_storage = true to ~/.codex/config.toml

codex-maintainers · 11 months ago

Thank you for the feedback! Please try again on the latest version of Codex CLI. If the issue persists, feel free to reach out with more details.