Why does my Amazon Q Business web experience return the error message "Sorry, I could not find relevant information to complete your request"?

Resolution

The "Sorry, I could not find relevant information to complete your request" error message can occur for the following reasons:

• You're using incorrect prompts for the document.
• There are access control list (ACL) issues for the document.

Check for valid prompts

Amazon Q Business doesn't return responses for meta or aggregation prompts or allow you to query specific documents or projects by ID or name.

For example, Amazon Q Business can't respond to the following prompts:

• "How many tickets are currently open?"
• "Print a list of Jira tickets related to my project."
• "What data sources have been indexed?"
• "What is contained in the data?"

When you send a query that's similar to "Find the document on project XYZ and summarize it," Amazon Q Business can't find the specific document. However, Amazon Q Business might respond with all documents that mention project XYZ, and then summarize the contents.

Create prompts that target specific documents

When you structure your prompt, it's a best practice to use the following structural elements:

• Primary ask: The action or information that you want Amazon Q Business to provide.
• Context: The additional context that Amazon Q Business might require to complete the request.
• Input data: Additional data points that might influence the response.
• Output request: The format that you want Amazon Q Business to provide the response in.

The following example prompt uses a Windows laptop user manual PDF file as the data source:

"What are troubleshooting steps for a Windows laptop that can't connect to Wi-Fi? I tried to update it and reset Wi-Fi drivers but the issues are persisting. Format the steps as bullet points."

The preceding prompt contains the following four elements:

• Primary ask: What are troubleshooting steps
• Context: For a Windows laptop that can't connect to Wi-Fi
• Input data: I tried to update it and reset Wi-Fi drivers but the issues are persisting
• Output request: Format the steps as bullet points

Note: To view sample prompts, activate Quick prompts in Amazon Q Business.

To create prompts that target specific documents, complete the following steps:

1. Open the Amazon Q Business console.
2. In the navigation pane, choose Applications, and then select the name of your application.
3. Under Enhancements, choose Data sources.
4. Under Data source, search for your data source name and confirm that the Last sync status is Completed.
5. Under Index, check the document count attribute to confirm that you added documents to the index.
6. Review the sync run history report to confirm that your document synced.
7. Create prompts that are specific to the information in the body of the document.
8. Send your prompt to Amazon Q Business, and then wait for a response.
9. To confirm that Amazon Q Business references the correct document, check the citation that Amazon Q Business returns in the response.

Check ACLs for the documents

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.

If you're using valid prompts and still experience the error, then check the ACLs for your source documents. When you turn on ACLs for your connector, Amazon Q Business returns only documents that include your username in the document's ACL.

Note: You can turn off ACLs. However, you must delete the data source and recreate it.

To confirm that your source documents appear in the ACLs, complete the following steps:

1. Open the Amazon Q Business console.
2. In the navigation pane, choose Applications, and then select the name of your application.
3. In the navigation pane, under Enhancements, choose Data sources.
4. Under Data source, search for your data source name, and then select your data source.
5. Choose the Sync run history tab, and then choose View report from the Actions column to open a new tab for Amazon CloudWatch Logs Insights.
6. Choose Run query.
7. Find your source document in the report, and then check the ACL column for the ACLs for your document.
8. Check the ACL to make sure that your username matches your email ID in AWS IAM Identity Center.
9. If the username and email ID don't match, then update your alias in the User Store to include the username from the ACL. Run the update-user AWS CLI command:

   aws qbusiness update-user \
     --application-id your_q_business_application_id \
     --user-id your_q_business_user_email \
     --user-aliases-to-update '[{"userId": "your_user_id_from_data_source"}]'

   Note: Replace your_q_business_application_id with your application ID, your_q_business_user_email with your user email address, and your_user_id_from_data_source with your user ID from your data source.
10. (Optional) To verify that your alias updated, run the get-user AWS CLI command:

    aws qbusiness get-user --application-id your_q_business_application_id --user-id your_q_business_user_email

    Note: Replace your_q_business_application_id with your application ID, and your_q_business_user_email with your user email address.
11. Sync your data source to update the ACLs for your documents.