Unknown errors when adding "Relationships" to "Topics" and related

Q&A
, ,
1

Hi!

We’re currently using Amazon Quick Pro to consume data from our AWS data lake through Athena, and we’ve been running into a few issues with Quick Agents using this setup:

Agent → Space → Topics

The first issue happens when we use Relationships inside a Topic.

We have some Topics with more than one dataset from the same source. The columns used in the relationships have matching values and no nulls.

The Agent can see the Topic, but when we ask *any* questions to that specific Topic, all queries fails. One of the errors returned by the Agent is:

{"error": "'QuickSight' failed in this request. To avoid repeated failures, please avoid using this service for this immediate request only. Future requests may still use service."}

If we remove the Relationships from the Topic, it starts working again. We tested the datasets using both SPICE and Direct Query and got the same behavior.

We are also seeing a similar problem with CLS.

RLS is already working correctly in these datasets. However, when we enable CLS on a dataset and use that dataset through a Topic, the Agent starts failing with generic errors. If we remove CLS, the same Topic starts working again.

For testing, we kept the CLS configuration very simple: a single restricted column using the same email address as the current Quick user.

The third issue is related to the number of Topics attached to a Space.

When we have more than 10 Topics in the same Space, the Agent seems to only consider 10 of them during the chat session.

For example, if we have 14 Topics attached, some of the other 4 are not available to the Agent. When trying to access one of those Topics, we’ve also seen errors like:

'<topic-id>' is not valid under any of the given schemas

I’m hiding the actual Topic ID here, but the value returned in the original error is the ID of the Topic that the Agent was trying to use.

If we remove some Topics from the Space or change which Topics are attached, previously unavailable Topics can become available again.

We couldn’t find this limit in the documentation. From what we found, a Space can contain up to 20 Topics, so we’re not sure if there is another undocumented limit on how many Topics an Agent can actually consider during a chat session.

So these are basically the three issues we’re trying to understand:

  • Relationships inside a Topic cause Agent queries to fail.

  • CLS works at the dataset level, but causes failures when the dataset is accessed through a Topic.

  • Spaces allow more than 10 Topics, but the Agent seems to only consider 10 of them.

Are these known limitations of Quick Agents/Topics, or are we missing some configuration?

Any documentation or guidance would be helpful. We also tried opening an AWS support ticket, but haven’t received a response yet.

2

Hi @Lucas_Martins,

Welcome to the Quick Community!

In terms of your first and second issues, that is definitely some interesting behavior and do not believe it should work that way. Your third issue is especially interesting, as Spaces should have a resource of limit of way more than 10.

The only action I can recommend for now is to wait on your existing support ticket, as they should be able to dig into the specifics on their end. If you do receive a response, please feel free to update this thread so that others with a similar use case can be informed as well.

Thank you!

3

Hi @Lucas_Martins,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.