Troubleshoot Postgres
Audience: Admins, Developers, Solution Architects
Purpose: Describes troubleshooting methods for issues with the Postgres integration
The following table presents solutions to common issues with the Postgres integration. For additional help, see the PostgreSQL documentation.
You receive an error message that reads: Error while using PostgreSQL Plugin.
You have bad database credentials, an unreachable host, or an invalid query.
Review the error message for more details. Update your integration secret or query, and retry.
You receive an error message that reads: Error decoding JSON .
Your integration secret isn't valid JSON.
Update your integration secret.
You receive an error message that reads: Expected a single value result, but the query returned multiple rows or columns.
The Return Single Value script input of the Read Data action is true, but the query selected more than one row or column.
Adjust your query to select exactly one value.
You received an empty string.
The query ran successfully but matched no rows.
This is expected behavior. An empty result returns "", not null.
Your result string is truncated.
The result set is larger than 5 MB.
Target your query with LIMIT.
What's Next
For details on reviewing your PostgreSQL configuration and integration secret, see Enable Postgres in Kizen. To access your database query, see Add Postgres Data to an Agentic Workflow.
Postgres, PostgreSQL, and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada. Kizen's PostgreSQL integration is not affiliated with, sponsored by, or endorsed by the PostgreSQL Community Association of Canada, the PostgreSQL Global Development Group, or the PostgreSQL Project.
Last updated
Was this helpful?