Unable to do Generative AI with uploaded documents

(1) Share

Report

Posted on by SilvermineAI

I have an issue with uploading documents for Generative AI in Copilot Studio.

I create a new copilot
I upload a PDF (i also try RTF of same content)
I wait 5 min
I ask very simple, directed questions
Bot is unable to respond - always goes to "Escalate" topic

I'm able to get answers when I put in a website.

I check Boost conversations under Analytics - it doesn't seem like GPT is even being called:

How do I get my bot to read my PDFs and give me something useful?

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

SilvermineAI 10 on at

Like (0)

Report

When I go to the data sources, I don't see anything about my document (I know I upload it under the "Generative AI tab").

Was this reply helpful? Yes No
roshur 5 on at

Like (0)

Report

Similar experience/problem here also today.

I've created a several copilots with varying sized/complexity excel files.
I've waited between 20 minutes and 2 hours after setting them up.
and they don't seem to ever try to use the excel file.
always goes direct to the escalation topic.

I've attached smallish/simple test file I created to just try to get this to work.
(this is all synthetic data)

SchoolGrades.xlsx

Was this reply helpful? Yes No
nicg 8 on at

Like (1)

Report

I have the same issue. Documents I upload to the bot are seemingly ignored. The same documents work great when sourced from SharePoint/OneDrive, so I don't believe it's an issue with the actual files.

My understanding is that, once files are uploaded, any generative answers nodes will use the files as sources by default. However, if I look at Analytics > Boost Conversations, there's no data, suggesting the feature isn't being used at all.

Was this reply helpful? Yes No
nicg 8 on at

Like (1)

Report

I've found that if I manually create a topic with a generative answers node, it does work. However, the system created "Conversational Boosting" topic does not. Somehow it appears to be related to the "Latency message" setting that the manually created generative answers node don't have.

Was this reply helpful? Yes No