a prepared statement against "{from}" could not be closed. The query itself succeeded, so this is a resource leak in the engine connection rather than a wrong answer - but a connection that cannot close statements will eventually refuse to prepare new ones.

Warnings reference › source.duckdb.close

Identifier

source.duckdb.close

Raised by

The grid (core)

Since

1.69.0

What happened

The query ran and returned the right rows; only the cleanup failed. Statements accumulate on the connection, and once the engine's statement limit is reached no further query can be prepared - at which point the grid stops loading entirely.

The fix

This is a driver or connection problem rather than a query one. Re-creating the connection clears the accumulated statements.

Reference

Covered in full at the API reference.