Assistant API - Error with files

Hi- I created an assistant that uses retrieval and I uploaded the files using the web interface. It works using the test playground but when I when I call it from the python API, I get this error:

Since you have uploaded a file that is not accessible with the myfiles_browser tool, I won’t be able to directly make use of the contents of the file for assisting you.


This is killing me. I have a 42% failure rate with reading files now, all with this kind of error. Sometimes re-running with the same file works, sometimes it fails. Seems like some data cluster consistency issue maybe?

1 Like

Painful :slight_smile:
Now I am getting this error:
It seems there has been a misunderstanding. The file you have uploaded is not accessible using the myfiles_browser tool as it may be.

It seems to cycle through a few different messages, all on the same theme of myfiles_browser not working.

FWIW - I added a 10 second delay between uploading a file and using it and it improved my success rate. Either that or something was fixed on the API side :upside_down_face:

I am also getting a lot of wonky behaviour with the Assistant API and files. Lots of “I cannot access the file” even though it was uploaded minutes ago, and it’s just a simple text file.

I just posted this in a different thread:

When I try to upload a .csv to the playground assistant I get this error:

Failed to create assistant: UserError: Failed to index file: Unsupported file file-tYMNCZxn29GoTc9xtg4kAu6D type: application/csv

Even though it is a correct .csv and the data is prepared properly.

Its frustrating not knowing if I’m doing something wrong or if this is to do with the outages or rollout.

Late last night I started getting a new error

openai.BadRequestError: Error code: 400 - {‘error’: {‘message’: “Failed to index file: () The index ‘document_chunks_hnsw_432’ for service ‘retrieval-search-index-prod-11’ was not found.\nCode: \nMessage: The index ‘document_chunks_hnsw_432’ for service ‘retrieval-search-index-prod-11’ was not found.”, ‘type’: ‘invalid_request_error’, ‘param’: None, ‘code’: None}

1 Like

Hi, did you find a fix for this ?