Power Platform Community Forum Thread Details

The screenshot indicates that the topic flow in Microsoft Copilot Studio is working correctly—the custom search node runs successfully and no errors appear. However, the retrievedContent output table is empty, meaning the retrieval service returned zero results, not that the process failed. This rules out licensing or quota issues, since those would produce explicit errors or failed nodes.

The most likely causes are related to the retrieval system rather than the topic logic. Common reasons include a stale or failed knowledge index, where uploaded files appear available but were not indexed properly; a search query issue, where dynamically generated queries become empty, overly long, or stripped of useful tokens after normalization; a broken data source binding in the custom search configuration; a language mismatch between the query and indexed documents (for example Arabic vs. English); or files that contain little extractable text due to size limits, scanned PDFs, or image-heavy content.

In short, empty search results usually mean the backend index or query handling is the problem. The recommended troubleshooting steps are to check file indexing status, rebind the data sources, inspect the actual generated query, test with text copied directly from documents, and re-upload a file to trigger reindexing. In most cases, fixing the index or source binding resolves the issue.

Reference Document-
1. Unstructured data as a knowledge source - Microsoft Copilot Studio | Microsoft Learn
2. Perform custom search - Microsoft Copilot Studio | Microsoft Learn