Responses API with file input in the background mode: server error with PDFs

API Bugs
1

For the last ~14h, we are having issues running Responses API in the background mode with file input.

We have tested with both gpt-4o-mini and gpt-5-mini. File upload works correctly.

To start the model, our input looks like this:
{
"model": "gpt-5-mini",
"instructions": "Our instructions",
"input": [
{
"role": "user",
"content": [
{
"type": "input_file",
"file_id": "file-ABC"
}
]
}
],
"background": true
}

This gives us ID in format “resp_XX” with status “queued”.

But when fetching status again in 10s, we get status “failed”, with error part:

“error”: {
“code”: “server_error”,
“message”: “An error occurred while processing your request. You can retry your request, or contact us through our help center at ``help.openai.com`` if the error persists. Please include the request ID wfr_019d1fe6f276773683c484e7582fbca3 in your message.”
},

We have used same pattern in our application for a while, it stopped working ~14h ago. And we noticed that this issue seems to happen with PDF files only. No issue with images (png, jpg).

1 Like
2

Same issue here exactly.
Here is another request ID if that helps : wfr_019d1f7156ba7bdca8eb2a5fc3637db3
With background false, it works with the same file id

3

Exactly the same error here (wfr_019d2097feee73b0a276090354a2104f)

¿Bug, update?…

4

Adding data points and a workaround.

I’m hitting the same issue with gpt-5 (gpt-5-2025-08-07). After isolation testing, the bug is specifically background: true + input_file in message content. The same files work fine when routed through code interpreter’s container.file_ids with background mode on.

The dashboard shows “No input items” for failed runs, but the payload is confirmed correct (logged exact JSON before POST).

Failed request IDs: wfr_019d1db3689f76e18b535c7462f92b59 wfr_019d1e013b797b878cf46f648d6374e7 wfr_019d1e1cbc3a796e86336959cc91b6ab

Workaround: Route files through code interpreter container.file_ids instead of input_file. The model can still read the file — it just spins up a container.

1 Like
5

this just started working again for us using input_file

1 Like
6

This also started working for us again!

1 Like