424 Failed to find index with name

[Joshua_Rowlison]

I’m trying to deploy an agent to do an end-to-end test on the process(taking a form response for disposing of an asset and creating tasks for the relevant teams).

I can sometimes get it to run in test on Studio but if I try to call it from other code or deploy it, I have only gotten it to work once. Otherwise it throws:

424 Failed to find index with name=Prompt Template
ErrorCode:Agent.BaseError
TraceId:2fcfe875a1aadd90883a44b3735b66ea
Tool of type Context failed because: Failed to find index with name=Prompt Template

To speed up this discussion,

1. I have tried deleting and creating the index in the folder my process lives in.

---

2. I’ve deleted and recreated it in the solution folder created at deployment

---

3. I’ve removed it from all locations and created the index from the agent itself.

---

4. I’ve removed it from all locations, created in the folder before adding it to the agent.

---

5. I am 100% certain it’s the correct tenant and folder, I think the Agent-solution process makes no sense when you can’t add most resources to that solution and I’ve been double-triple checking things because I don’t trust it.

---

6. The index works, I’ve had a handful of successes when I ran in debug/test in studio directly.

---

7. I’ve made sure when removing the context to also remove it from the solution folder, close and reopen the solution to ensure it’s not there.

---

8. I’ve deleted and recreated the deployment multiple times

---

9. I’ve deleted and recreated the solution.

---

10. Sometimes when attempting a deployment I get the below error and it hangs permanently. I have to publish a new version, nothing else will fix it.
    
    

---

11. View of the index list for the folder

View of the process sitting in the folder(note the unknown status for the index in the same folder)

View of the agent definition and the window showing both that the folder does have it and also that the index is found in the location from the Agent Builder

[V_Roboto_V]

Hi @Joshua_Rowlison

I tried replicating your issue, It shows “Unknown” Status:
In my case, I used index from a different folder. There is no index in the Solution Folder

Please try the following Solution:

1. Go to “Edit” option of the Agent
   

   

2. Then, Go to “Package Requirements” → “Overwrite”

3. Click on the Index that you really want the Agent to map to.
   

   

4. The status MUST CHANGE to Available. Then click “Update”
   

   

Please run the Deployed Agent again, and let me know.

If this solves your issue, Do mark it as a solution.
Happy Automation

[Joshua_Rowlison]

Hello, thanks for the advice, I was able to alter the process to overwrite the index and change it to available. It seems the first deployment probably rolled out the index in the solution and then subsequent deployments see the change to use that copy but the process itself never gets updated. Or something in that area.

As you can see in my first post the index does live in the folder created by the solution, which as far as I can tell shouldn’t be a problem.

Unfortunately, when I attempt to trigger the agent from my process as before, I get the same error.

[Joshua_Rowlison]

Second follow up, for folks that might have the same problem, V_Roboto_V’s answer was the bulk of the problem, additionally make sure the account you’re using has access to the index, I’m in dev so I just made my bot a folder admin and it worked, so I cannot say what it needs but I’m betting View Index would be enough.