Troubleshooting common errors
A single reference for the errors AI Insights users most commonly see.
"Named Pipes Provider, error: 40 - Could not open a connection to SQL Server"
The cloud tried a direct connection to an on-prem server it can't reach. Toggle Route via Gateway on the datasource and pick your gateway before clicking Test.
"Gateway did not respond in time"
The gateway is offline. Check Settings → Manage Gateways → Last heartbeat. If older than a minute, restart the gateway app on the on-prem machine.
"0 fields loaded" / "No tables were discovered"
Connection succeeded but the SQL user can't read INFORMATION_SCHEMA. Grant VIEW DEFINITION or add the user to db_datareader.
"AI service is rate-limited (Cohere 429)"
The AI provider throttled the request. Wait the retry-after seconds shown in the error. If on a trial Cohere key, upgrade to Production.
"Email send failed" but the email arrived
This was a false positive when the SMTP server hung up abruptly after delivery. Fixed in v1.0 — the system now correctly reports success in this case.
Charts in a published report render empty
The report's charts are bound to a REST API or File URL datasource. Confirm window._rvDatasourceTypes in page source includes your datasource type — if it's {}, the controller's metadata pass isn't running (rebuild).
"An unexpected error occurred"
Check the server log for the actual exception. Most often: a missing column in a manually-edited table. The startup seeder's heal pass restores them on next restart.