Empty results
An empty result is not always an error. It can mean nothing matched, or that something is scoping the data out.
Common causes
There genuinely is no matching data.
A filter or date range is too narrow.
The wrong workspace, connection, or thread is selected.
A relevant table or column is hidden.
The read-only database user lacks access to the data.
In Odoo, the company or user scope excludes the records.
The data is stored differently than expected.
What to check
Broaden the filters or widen the time range.
Ask a simpler count or list question to confirm data exists.
Verify the workspace and the connection the thread is using.
Check AI Guide table visibility for the data you expect.
Check the Odoo company and user scope if you are using Odoo.
Compare with the source application or a database report.
If the data clearly exists in the source but STYD returns nothing, contact STYD so the connection, visibility, and scope can be reviewed.