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
tvriesde
changed the title
[BUG] Created connection not working
[BUG] Connection for Azure OpenAI not working when following README procedure
May 21, 2024
Hi @tvriesde , thanks for reaching us. The 'deployment name' is not part of connection, it was on the flow node in flow.dag.yaml if you are using the llm node to make the openai call. For example:
Hi @tvriesde , thanks for reaching us. The 'deployment name' is not part of connection, it was on the flow node in flow.dag.yaml if you are using the llm node to make the openai call. For example:
Describe the bug
After creation of connection using the README instructions for Azure OpenAI I get error:
pf.flow.test failed with UserErrorException: Exception: OpenAI API hits NotFoundError: Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}} [Error reference: https://platform.openai.com/docs/guides/error-codes/api-errors]
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:
as API_BASE i've used: Azure OpenAI Endpoint -> "https://something.openai.azure.com/"
as API_KEY i've used: Azure OpenAI Key1
Error message:
OpenAI API hits NotFoundError: Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}} [Error reference: https://platform.openai.com/docs/guides/error-codes/api-errors]
pf.flow.test failed with UserErrorException: Exception: OpenAI API hits NotFoundError: Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}} [Error reference: https://platform.openai.com/docs/guides/error-codes/api-errors]
azure_openai.yaml content:
$schema: https://azuremlschemas.azureedge.net/promptflow/latest/AzureOpenAIConnection.schema.json
name: open_ai_connection
type: azure_open_ai
api_key: ""
api_base: ""
api_type: "azure"
I would expect that I also have to supply the deployment name but don't find the option.
The text was updated successfully, but these errors were encountered: