You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Azure, deployments are often named other things than the model names, for instance "gpt-4o" could be named "wrapper-api-gpt-4o". This causes the mapping to not recognise the model since it is not in the mapping json.
I would suggest an additional parameter that differentiates the deployment name used for querying the api vs the model selector.
Relevant log output
No response
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
What happened?
In Azure, deployments are often named other things than the model names, for instance "gpt-4o" could be named "wrapper-api-gpt-4o". This causes the mapping to not recognise the model since it is not in the mapping json.
I would suggest an additional parameter that differentiates the deployment name used for querying the api vs the model selector.
Relevant log output
No response
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: