Share
ReportI'm building a Copilot Studio agent to answer questions based on survey responses stored in a SharePoint list. The list (11 items, columns: Single line of text, Date and Time, Multiple lines of text, Choice, plus the default Created By/Modified By Person or Group columns) is populated by a separate Power Automate flow that parses uploaded PDFs.
A few days ago I successfully added this exact list as a knowledge source and it worked fine. I later removed it because I suspected it wasn't reflecting the latest data, intending to re-add it. Since then, every attempt to re-add it immediately shows "Error" in the status column, with no error message or detail surfaced anywhere in the UI.
What I've ruled out so far:
- Permissions: I created and own the list myself.
- List size: only 11 items, well under any threshold.
- Column types: all standard types (text, date/time, choice, person/group for the default columns).
- Agent-specific config: I tested by adding the same list to a brand-new, unrelated agent - same immediate Error.
- Tenant-wide restriction: since it worked days ago and nothing was changed at the tenant/policy level in between, a Restricted SharePoint Search-type setting seems unlikely.
- List categorization: the list only appears under "Recent Lists" (not "My Lists") in the Add Knowledge picker, which I understand is expected since it wasn't created in the standalone SharePoint Lists app.
- Permissions: I created and own the list myself.
- List size: only 11 items, well under any threshold.
- Column types: all standard types (text, date/time, choice, person/group for the default columns).
- Agent-specific config: I tested by adding the same list to a brand-new, unrelated agent - same immediate Error.
- Tenant-wide restriction: since it worked days ago and nothing was changed at the tenant/policy level in between, a Restricted SharePoint Search-type setting seems unlikely.
- List categorization: the list only appears under "Recent Lists" (not "My Lists") in the Add Knowledge picker, which I understand is expected since it wasn't created in the standalone SharePoint Lists app.
Given it worked before I deleted it and now fails consistently (including on a fresh agent), my best guess is something related to a stale/orphaned reference to the list from the original add, or a broken SharePoint connection reference tied to my account - but I don't have visibility into what's actually failing since the UI gives no error detail.
Has anyone seen this specific pattern (worked once, broke after delete + re-add, fails silently even on new agents)? Any way to get more diagnostic detail than the bare "Error" status, or a known fix for this?
Categories:
I have the same question (0)
All responses (
Answers (
160
