Chat Limitations
Last updated
Last updated
We're continuously working to improve the quality of the responses. Here are the current limitations.
Lumi cannot answer questions requiring data it isn't connected to or aware of in the knowledge base. Questions beyond this scope may not receive accurate responses. You can check what data is available to query in the table preview.
Misspellings in attributes (e.g., product names, brands, or categories) may lead to empty responses. If unsure, users can:
Perform a general search: "how many items fall under the category that contains any variation of bikes in the description?"
Add common abbreviations or variations to the knowledge base.
Scenario: User asking about metrics related to 'carbon road bike' sales
Error: There are no items that have the name 'carbon road bike'. This will return nothing. Lumi is directly filtering for items with the explicit name 'carbon road bike'.
Additionally this is an example of vague prompting. Is this a category, a brand, or an item? For more information view Prompting Best Practices.
Use the exact attribute name.
Example: What was the revenue of the item 'Carbon Elite Road Bike' last year?
Lumi includes follow-up questions in responses to encourage further user engagement. Please note that some of these follow-up questions might not always be directly relevant.
To ensure that raw data is handled correctly, Lumi does not have access to the previous query data results. This means that prompts need to be structured with this in mind and should not reference data returned. Rather a rephrased prompt can be used to target whatever insight is desired.
To ensure unnecessary computation resources do not occur, a default limit is enabled to 25 records. In some cases this might cause some expected information not to be shown due to this limit. To modify these settings and view more information review Organizational Query Row Limit Settings.
