One of my custom chat agents keeps referring to an Amazon Quick Space that is not configured in that chat agent’s knowledge sources. This is causing noticeably slower response times for the agent.
The Issue:
The space does not appear in the agent’s linked knowledge sources
Despite this, the agent continues to reference content from this space
Response times are significantly impacted
What I’ve checked:
Confirmed the space is not listed in the agent’s knowledge source configuration
Verified this is a custom chat agent, not the system default agent
Request: I need guidance on how to sever the connection between this specific chat agent and the space, or escalation to the appropriate team to investigate why the agent is accessing a space that isn’t configured in its settings.
That is a very interesting behavior that I have not seen before here on the community. You have already confirmed that the space is not linked to the agent’s knowledges sources. When you have the agent selected, is there any spaces you may have accidentally attached within the chat agent’s data and apps? Within this drop down, you can select other quick assets that are not linked to the agent’s knowledge sources and attach it to the custom agent. That is the only thing I can think of that may be linking the space to your agent. Please refer to the screenshot below on the drop down that I am talking about:
If you confirm that there is no direct connection of the space to the agent through this route, then my next suggestion is to create a support ticket, and the support team will be able to further investigate into this instance. Please refer to this resource on how to create a ticket (Case management - AWS Support).
Ah you’re a hero - the chat agent was set to get answers from “All data and apps” including the Space in question. Changing the selection to “General knowledge” only seems to have stopped the review of this Space’s extensive library, thereby cutting down the response time - thank you!
