User is missing required index permissions after solution deployment

Why does the agent fail with a "Failed to find index" error after deploying a solution for the first time?

Issue Description


When a solution is deployed in UiPath Orchestrator for the first time, it automatically creates a subfolder under the selected parent folder and places all solution components — agents, jobs, and processes — inside that subfolder. The deployed agent looks for the Context Grounding Index within its own solution subfolder. Since the Index resides in the parent folder, the agent cannot resolve it and the following error is thrown at runtime:

Failed to find index with name = <index_name>


Resolution

  1. While deploying the solution, navigate to the Review section.
  2. Locate the Index entry in the review screen.
  3. Click the button labelled Link to Existing.
  4. Point it to the Index in the parent folder where the Index actually lives.
  5. Complete the deployment. The agent will now correctly reference the Index from the parent folder.


If the solution is already deployed and the agent is throwing the error, follow these steps without redeploying:

  1. Navigate to the deployed Agent or Job in Orchestrator.
  2. Click Edit.
  3. Update the folder reference to point to the parent folder where the Index lives.
  4. Save the changes.

Note: This manual correction may need to be repeated if the solution is redeployed. Using the Link to Existing option during the Review step at deployment time is the recommended long-term approach.