[BUG] Azure.AI.OpenAI.Assistants - I'm not able to ask question about the content of a file uploaded in the Storage #44197
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
OpenAI
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Service Attention
Workflow: This issue is responsible by Azure service team.
Library name and version
Azure.AI.OpenAI.Assistants 1.0.0-beta.4
Describe the bug
Hello,
I've developed a chatbot in .net c# and I use the library Azure.AI.OpenAI.Assistants.
I have pre-created my Assistant in the web interface of OpenAI (I didn't attached any document directly to the assistant).
In my application, I upload a document (role=assistant) on the Store of OpenAI and I get back its identifier (file-wXz...) then I create a message and I pass the collection of file_ids (actually I've only one id) in the following function:
Response<ThreadMessage> messageResponse = await client.CreateMessageAsync(thread.Id, MessageRole.User, userMessage, **file_ids**, null, cancellationToken);
I submit my message with a question about the file content by creating a run.
The answer of the model is still something similar to:
I am unable to access the content of the file you uploaded. Could you please try uploading it again so that I can assist you in understanding what the document is about?
What I do wrong? Can you please help ?
Expected behavior
The model answers with information retrieved from the document.
Actual behavior
I receive the following message from the model:
I am unable to access the content of the file you uploaded. Could you please try uploading it again so that I can assist you in understanding what the document is about?
Reproduction Steps
Environment
Windows Server 2019 , .NET runtime version 6, Visual Studio 2022
The text was updated successfully, but these errors were encountered: