Error in POST handler: Error: 400 Invalid 'tools[0].vector_store_ids[0]': string does not match pattern. Expected a string that matches the pattern 'vs_*'

[ekeric13]

Trying out the demo and i get an error as it seems to be having issues with the tool search api

[ekeric13]

okay fixed. The problem was clearly it wasn't recognizing my vs id but i did add it and i even restarted the server... maybe i forgot to save the file. regardless got it working after i came back an hour later and simply just tried again!

hit another roadblock though:

  {
    role: 'user',
    content: 'i am wondering what my latest orders are?'
  },
  {
    id: 'fc_6801d98b556c81929eb374a2f2728529080978bc749cb407',
    type: 'function_call',
    status: 'completed',
    arguments: '{"user_id":"user123"}',
    call_id: 'call_zoEzANXzotmAw3BV2xKV6hFK',
    name: 'get_order_history'
  },
  {
    type: 'function_call_output',
    call_id: 'call_zoEzANXzotmAw3BV2xKV6hFK',
    status: 'completed',
    output: '["ORD1001","ORD1002","ORD1003","ORD1004","ORD1005","ORD1006","ORD1007"]'
  },
  {
    id: 'fc_6801d990b7dc8192a32f14f07fc66388080978bc749cb407',
    type: 'function_call',
    status: 'completed',
    arguments: '{"order_id":"ORD1007"}',
    call_id: 'call_JBNbh2goyCLBdINhZ3yxxBYx',
    name: 'get_order'
  }
]
Error in POST handler: Error: 400 No tool output found for function call call_JBNbh2goyCLBdINhZ3yxxBYx.
    at async POST (app/api/turn_response/route.ts:12:19)
  10 |     const openai = new OpenAI();
  11 |
> 12 |     const events = await openai.responses.create({
     |                   ^
  13 |       model: MODEL,
  14 |       input: messages,
  15 |       tools, {
  status: 400,
  headers: [Object],
  request_id: 'req_f2c6e24d6c723d3f4e0c706bf85b62c3',
  error: [Object],
  code: null,
  param: 'input',
  type: 'invalid_request_error'
}
 POST /api/turn_response 500 in 456ms

[katia-openai]

Hi @ekeric13, glad you solved the vector store ID issue.
For the 400, I think it's an issue with the fact that the function call are handled inside streaming events and when the events arrive out of order, the next tool is handled before the previous tool output was submitted.
Will take a look, thank you!