Troubleshooting Queries
Learn how to troubleshoot new Queries you are developing or launching
Resources to help you troubleshoot Queries
Chat Card Response Messages
API Playground
Before you start, make sure...
You have the access to the Queries Workspace
Issue: You cannot save my Query
Symptom
You see error: There was an error saving your change when trying to launch a use case, at the very end.
Possible Cause
You have selected "this lookup requires 1 keyword", but have not specified the expected keyword. Your use case requires a keyword to be specified.
To Fix: Go to the "Triggering and parameters" tab and select "This lookup requires one keyword". Then, click "Add Slot" and enter the expected value for the slot, given your example utterance.
Possible Cause
You have selected "this lookup requires no keyword", but have specified an expected keyword. Your use case does not require a keyword to be specified.
To Fix: Go to the "Triggering and parameters" tab and select "This lookup requires no keyword". Then, click "Add Slot" and enter the expected value for the slot, given your example utterance.
Possible Cause
You have specified a slot value that does not exist in the example utterance
To Fix: Go to the "Triggering and parameters" tab and select "This lookup requires no keyword". Then, click "Add Slot" and enter the expected value for the slot, given your example utterance.
Issue: Your newly configured query does not appear in chat
Symptom
I see I could not find any results directly related to your request message in chat
Possible Cause
You have not launched to relevant users
Possible Cause
The utterance was not judged to be relevant to any configured use case
Possible Cause
Business Queries is not enabled for your organization
Possible Cause
Utterance judged to be outside of boundary of any configured use case
Possible Cause
Utterance value does not match expected API value (entity mismatch)
Possible Cause
You have specified full uttterance as the keyword
Possible Cause
Target user does not have access to the bot
Issue: Query is partially / fully empty
Symptom
You see a card with missing fields, or no fields at all