OpenAI background mode, ZDR, store=true, and retention limits
OpenAI background mode, ZDR, store=true, and retention limits
Section titled “OpenAI background mode, ZDR, store=true, and retention limits”Background mode is attractive because it lets long-running work continue after the initial request. For enterprise teams, the harder question is data control. A background response needs retrievable state. That makes it different from a stateless synchronous call, and it changes which workloads should be allowed onto that lane.
This is not only a compliance footnote. It is an architecture boundary.
Current official signals checked April 24, 2026
Section titled “Current official signals checked April 24, 2026”| Official source | Current signal | Why it matters |
|---|---|---|
| OpenAI background mode guide | Background mode stores response data for roughly 10 minutes to enable polling and is not Zero Data Retention compatible | Teams with strict ZDR expectations should not treat background mode as a drop-in replacement for stateless requests |
| OpenAI background mode guide | Background sampling requires store=true; stateless requests are rejected | The long-running job model depends on stored response state |
| OpenAI data controls documentation | Background mode data storage for polling is called out separately from normal response behavior | Data-control review should happen before moving sensitive jobs into background mode |
The practical rule
Section titled “The practical rule”Use background mode only for workloads where stored response state is acceptable under your data-control policy.
If a workload requires strict Zero Data Retention behavior, background mode may be the wrong runtime lane even if the task is technically long-running.
That creates a three-part decision:
- Does the job need long-running execution?
- Does the product need polling or later retrieval?
- Is stored response state acceptable for this data class?
All three need to be true.
Why background mode needs stored state
Section titled “Why background mode needs stored state”A background job must be retrievable after the initial request. The product may need to poll status, reconnect a UI, recover from a dropped stream, cancel a response, or fetch the final output. Those behaviors require provider-side state for the duration of the background workflow.
That is the tradeoff:
- background mode improves reliability for long-running tasks;
- stored state enables polling and recovery;
- strict statelessness becomes harder or unavailable for that lane.
The architecture should make that tradeoff visible.
Workloads that usually fit
Section titled “Workloads that usually fit”Background mode can be a good fit for:
- long research jobs using non-sensitive sources;
- document transformation where retention is allowed;
- internal report drafting;
- coding-agent analysis where repository data is approved for this lane;
- review-gated generation where the output is not immediately published.
The common pattern is that the organization accepts temporary stored state in exchange for a healthier long-running workflow.
Workloads that need more caution
Section titled “Workloads that need more caution”Be careful with:
- regulated customer data;
- sensitive internal investigations;
- confidential legal or financial material;
- highly restricted support tickets;
- workloads contractually requiring ZDR or equivalent handling;
- data that should not be retrievable outside a live request.
For these workloads, teams may need a different architecture: synchronous constrained calls, internal processing, a separate provider configuration, or a product-owned workflow that avoids background storage assumptions.
Policy should be attached to job type
Section titled “Policy should be attached to job type”Do not make data-control decisions one request at a time. Attach them to job types.
| Job type | Background mode default |
|---|---|
| Public-source research | usually allowed |
| Internal low-sensitivity drafting | often allowed |
| Customer-support analysis | depends on data class |
| Legal or regulated document review | usually needs security review |
| High-sensitivity customer data | avoid unless policy explicitly permits |
This keeps engineers from discovering the data-control problem during incident review.
Implementation checklist
Section titled “Implementation checklist”Before enabling background mode for a workflow, answer:
- What data class does the job process?
- Is temporary stored response state acceptable?
- Does the workflow require polling, cancellation, or later retrieval?
- Is the job compatible with the organization’s ZDR expectations?
- Should this job type be blocked from background mode by policy?
- Does the audit trail record why background execution was allowed?
- Is there a fallback lane for sensitive work?