OpenAI Assistants - vector search behavior inconsistency

I’m having an issue where my OpenAI Assistant has no problem accessing files in the Vector Store (in this case, a PDF) when I use the Playground in the OpenAI UI. Correct answers, great performance, no issues.

But when I ask the same questions through make.com, I get a response that the files are unable to be accessed. AFAICT all the settings are set correctly, and other aspects of the Assistant seem to work fine when accessing via make. Any ideas?

same problem here, always get messages back from assistant that it has problems processing files in the vector store.

I was able to fix it by moving from GPT4o to GPT4.1

1 Like

Hello everyone,
My scenario had been working perfectly for several months, but since last night, I’ve been receiving an error related to OpenAI.

The scenario uploads a file to OpenAI, transfers it to a vector store, and then analyzes the file through an assistant.

However, for the past ten hours or so, OpenAI has been returning an error stating that “It seems there is a technical issue with file search. I can’t access the data to retrieve the laboratory analysis results.”

Is anyone else experiencing this issue? Is it a technical problem on OpenAI’s side? Or has something changed that requires me to update my module configuration?

Thanks in advance!

@Turtle_System_SAS same here. Was working till yesterday and now I get the same error. Openai status if operational so something might have changed in the API maybe?

ok let me try this one

same problem here.
OpenAI Dashboard: If I create a new vector store in openAI and create an assistant from the VC then it always gives errors: An unexpected error occurred: Invalid URL (GET /v1/vector_stores/vs_6850129d2074819189372de9aed62674/associations)
under the part: “vector stor used by”

I was able to fix it by moving from GPT4o to GPT4.1

Thanks, I’ll give this a try. I’ve been learning how to use the Gemini modules in parallel, in my case I can stuff the files (a short JSON file) into the context window, but the Gemini module has its own issues.

Seems to have worked, thanks.

1 Like