Response.file_search_call.in_progress triggering way too late

API
1

Wondering if anyone else is experiencing same:

Using ResponsesAPI, and File Search tool, the tool itself works great, but the notification that a file_search_call.in_progress delays until right before the stream starts. The experience then is a delay to the frontend in knowing that a file search has been requested until the results are streaming back. There’s a brief flash of our message to the user, before it quickly gets overwritten by the stream.

I would think that the initial response.file_search_call.in_progress should come right as the request is made internally, yes? Or is this what we should expect?

1 Like
2

What you observe may be that:

Running non-generative embeddings on a short tool query made by AI and programmatic retrieval of information does not take much time - Vector store retrieval can be nearly instant.

How long does Google take to return the entire Internet to you? :innocent:

1 Like
3

Fair enough! I guess I assumed it would take as long as it does in ChatGPT, but they’re probably doing more than just repeating the response - thanks!

1 Like