Interesting, thanks! So you add a second “try again” message to the thread, after providing the fileIds+query and before running the assistant?
I just tried that, it seems to work okay. At least it didn’t complain yet that it couldn’t find the files - although that happens very irregularly it seems.
In my case the responses with this are still very lengthy, i.e. the assistant gives very verbose updates on which files it checked, where it didn’t find something and is looking next, but eventually it seems to find the information. But it still doesn’t seem to be able to answer more detailed or complex questions, which it used to do.
I still remember one month ago just uploading 10-20 files and the assistant being able to retrieve information quickly, without the verbose updates. It still seems like OpenAI nerfed it a lot since then, due to performance issues or something else. Really hope they bring that back. Annotations were also sporadically appearing, but haven’t seen them anymore since a week. Such big potential if they make that work.
Yes, in my case there is (until now) 100% success rate. It happened to me where the assistant answered with “I can’t find the things you search, let me try in another way” but I think that is related to the code_interpreter tool, which i’m not using here.
I was suffered the same issue and it bothers me several days, eventually I solved it with just simple prompting, shared my experience here:
I shared my solution in this post:
Is it happening with the public-facing GPT service? Perhaps, given the imminent launch of the GPT Store, fixing this for the API isn’t prioritized. Understandable, if so, but a bit frustrating!
This seems to happen when one file is accessed by multiple threads:
the first test thread succeeded in getting the assistant to read the file,
but the second test thread got a response that the file could not be opened.
Response: I cannot access the uploaded file using the myfiles_browser tool. Please re-upload the file.