Incorrect Interpretation in Chat agent's Amazon Q despite Explicit Instructions

In Amazon Q, the interpretation is incorrect for the time period being given in the question. I’ve tried multiple attempts with various prompts, and even after explicitly adding the instruction in the reference document section in the chat agent, the issue persists. Attaching the screenshots for reference.
chat agent: https://us-east-1.quicksight.aws.amazon.com/sn/agents/61250cc7-ce29-4576-9f53-0e13bf3cc9b0

Instructions given in the ref document in chat agent:

ERROR HANDLING PROTOCOLS

Time period mismatch detection:

REQUEST: "Time period mismatch detected. Requested [X period] but found [Y period] data. Please try retrieving data for the correct time period from the topic again

No data available:

Data validation failed. You requested Week 48 2025, but available data shows Week 48 2024. Please try again to retrieve the correct data for Week 48 2025 from the topic.

Hi @bagapriy and welcome to the Quick Suite Community!

For future reference, this is a public user forum, so the link you provided for your environment is something that I, and the other Quick Suite experts, cannot access.

For your question, that is interesting that the chat agent is misinterpreting your year. The chat agent is still a relatively new feature, so some bugs are expected. Moreover, one thing I have learned is refreshing your page can sometimes be an easy fix or some community users have noted that changing your internet browser (i.e. Microsoft Edge to Google Chrome) can sometimes be a solution as well.

If that doesn’t work, then the issue might pertain to your datasource. In your screenshots, it does note that there is not data available for ‘Week 01 2026’ yet. Sometimes reformatting your data can help with the chat agent’s querying capabilities.

Lastly, if that all does not work then I would recommend submitting a support ticket. Submitting a support ticket will allow the support team to further investigate the issue you are experiencing and may uncover the cause of it. Please refer to this resource on how to submit a ticket (Case management - AWS Support).

I hope this helps and please let me know if you have any further questions about this topic!

Hi @bagapriy,

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

Hi @bagapriy,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.

Thank you