Hey, I didn't change my function at all and suddenly I started receiving an error. I changed only analysisPlan, but didn't touch the function that there are warnings for. Call ID: 4ebed90b-190b-475e-8220-57664480fdb9 Could you please look at it?

what type of Error? I think i have the same issue with "pipeline-error-azure-openai-llm-failed"

We’re suddenly encountering the same issue

pipeline-error-openai-llm-failed

, seemingly out of nowhere—this may be OpenAI specific. We haven't made any changes to app code or assistant responses.

Model request failed (attempt #10, reason: (Invalid schema for function 'schedule-a-callback': In context=(), 'additionalProperties' is required to be supplied and to be false.))

It looks like on the server side, vapi might not be setting the

additionalProperties

field, while OpenAI’s api is now expecting it. This could indicate a recent regression or an unannounced contract change on OpenAI’s side, possibly introduced this afternoon. This is impacting functionality, and we need support. Please advise on how we can proceed. @User

This error message indicates there's an issue with the schema definition for the terminBotSilentTrigger function. The error occurs because the function's schema is missing the additionalProperties: false property, which is required to strictly enforce the schema structure. To fix this error, you need to modify the function schema to include additionalProperties: false in the parameters object. Here's how the function schema should be structured:

{

  name: "terminBotSilentTrigger",

  function: {

    parameters: {

      type: "object",

      properties: {

        // your existing properties here

      },

      required: ["your_required_fields"],

      additionalProperties: false  // Add this line

    }

  }

}

The additionalProperties: false setting ensures that no unexpected properties can be passed to the function. This is a security best practice as it prevents potential injection of unauthorized properties and It follows OpenAI's function calling schema requirements

Ohh wow, thank you!🤝

{
          strict: true,
          name: "...",

          description: "...",
          parameters: {
            type: "object",
            properties: {
               ...
            },
            required: ["..."],
            // @ts-ignore
            additionalProperties: false
          },
        }

@Shubham Bajaj But at the time when this error occurred, I had already included this (though Node.js threw a type error because the key did not exist, so I don't know if the VAPI SDK actually sent it). But the error resolved itself over time on my end without changing the function schema. :)

Hello Titaniumbach, could you please share the call ID and SDK name that you are referring to?

It's true that I don't remember seeing this paramter in docs. That's why I didn't have it in my code. Haven't tried it yet. I don't touch stuff that's not broken.

I am using NodeJS ServerSDK and callId was

6d1babfe-4e3e-489b-9d4d-773a6959f25a

But it's fixed now and happend only at this time where this issue was created