Error streaming run: Failed to fetch

API Bugs
, ,
1

All Assistant runs with file attachments fail in the OpenAI portal with the following message although these are same assistants that used to work , I wrote to support but no response

“Error streaming run: Failed to fetch.”

No cache/browser/machine fix works — this is reproducible across our org.
The same Assistants + files work perfectly via Postman/API, proving the backend is healthy.

DevTools shows no /runs request fired, confirming a portal-side CORS or signed URL bug.
Needs urgent attention — blocking enterprise testing.

1 Like
2

How are you getting there in the UI? The assistants dashboard is requiring you to pick “edit” to interact and “test” an Assistant: a very poor way to offer it to any other enterprise users.

Is this a thread vector store with “file search” enabled that you are attempting?

Assistants, (at least, vs Responses and its distasteful “prompts”) can be completely managed through API calls.

Checking - confirmed “attachment” failure with an existing Assistant ID that already has a vector store and file search:

image
image485×113 3.26 KB

The thread ID was created, but has no content.

It also isn’t great that the only place to see a viewed thread ID in the UI is in the URL bar.

Not going to go so far as to run scripts to attempt the same.

It seems there is a saboteur at work, that really wants developers to leave the OpenAI API, across multiple endpoints.