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
The different job ids were me filling in the blanks of my azure_endpoint. I noticed that the Llama Parse Docs require the azure_endpoint to be beyond "https://.openai.azure.com/" unlike the AzureOpenAI LLM object so the job IDs were me testing
Just "https://.openai.azure.com/"
Up to f"https://{org}.openai.azure.com/deployments/chat/completions?api-version={version}"
"https://{org}.openai.azure.com/deployments/chat/completions?api-version=<{version}>" with the extra "<>" in front of {version}
Describe the bug
I was following this example notebook on Llama Parse but was unable to replicate the results using my gpt4o model on Azure OpenAI.
Files
The file I used is available in the example notebook on llama parse
Job IDs
286f9c91-2244-4bce-bf40-624246be8f75
a77c610c-e2be-4d47-8849-09295b26677e
1fa80bba-a23f-4818-b2d2-6e2ace6c1d05
The different job ids were me filling in the blanks of my azure_endpoint. I noticed that the Llama Parse Docs require the azure_endpoint to be beyond "https://.openai.azure.com/" unlike the AzureOpenAI LLM object so the job IDs were me testing
** Code **
** Results: **
Documents full of "NO_CONTENT_HERE".
Client:
Please remove untested options:
The text was updated successfully, but these errors were encountered: