Real Postgres, MySQL, and SQL Server errors for AI agents

When a query against your PostgreSQL, MySQL, or SQL Server database failed, agents used to get a generic "Database query failed" with no detail. That hid real SQL mistakes, like a misspelled column or a missing join, from the agents that could have fixed them. Now the agent sees the database's own message and corrects the query itself.

How it works

• Classified at one boundary. A rejected query returns the database's own message, a statement timeout and an unreachable server each get their own status, and a refused login is reported as such.
• Clear connection errors. When you connect a database that refuses or can't be reached, you see the server's own reason instead of a generic failure.
• Platform faults read as platform faults. Internal errors and overloads in our hosted databases are reported as service problems, not as mistakes in the agent's query.

Your hosted workspace databases get the same treatment.