Model.property urlrequestmetadataenabled exsistzerver url must be valid url error I don't understand why I'm getting this @Vapi

@brandon holley It sounds like you're encountering an error related to a property called

urlrequestmetadataenabled

in your model, which requires a valid URL for the

exsistzerver

parameter. This error typically indicates that the URL provided does not meet the expected format or criteria for a valid URL. To resolve this issue, please ensure that the URL you are providing is correctly formatted and is accessible. A valid URL should start with

http://

or

https://

and should not contain any spaces or invalid characters. If you're sure that the URL is correct and you're still facing this issue, there might be a problem with how the URL is being parsed or used within your application. In that case, please check the documentation for the specific API or framework you are using, or reach out to their support for more detailed assistance. If you need further help with this, could you please provide more context or details about where and how you're using this property?

I need further assistance. I have tried using no server URL and a server URL that has been working in the past. I get the same error no matter what. @Vapi

@brandon holley I'm sorry to hear that you're still experiencing issues. It seems like there might be a problem with the configuration or the way the URL is being processed. To assist you further, I'll need some additional information: 1. Can you confirm that the URL you are using is indeed accessible and that there are no current issues with the server it points to? 2. Have there been any recent changes to your system or the API that might affect how URLs are handled? 3. Is there any additional error information or logs that you can provide which might give more insight into the issue? In the meantime, please double-check the following: - Ensure there are no typos in the URL. - Verify that the URL is complete and includes any necessary path or query parameters. - Make sure that the URL is being passed to the correct parameter in your API call or configuration file. If you've confirmed all of the above and the issue persists, it might be best to reach out to the support team of the API or service you're using with the specific details of the error. They may need to look into their system to identify the cause of the problem. If you can provide any additional context or details, I'll do my best to help you resolve this issue.

@User Hello, could I get some additional support on this?

@brandon holley can you try creating a new assistant, it's one of the chances your getting this by mistake. Do let me know how it goes.