We have observed that Ask Eddy does not return answers for user queries when the relevant knowledge base content is stored within large tables (70+ rows) or tables divided into multiple sub-tables. As a result, queries such as error code lookups (e.g., “Error code 2009”) return No Results Found, even though the information is present and published in the knowledge base.

We request an enhancement to improve Ask Eddy’s indexing and retrieval capabilities for large and segmented table content to ensure accurate response generation from structured data.