SQLStreams

the messaging platform that is just Postgres

You last visited on 9999-99-99 Show what's new since then

Error codes

Edit this page
Posted: 2026-09-09 · Report this thread
brandon Site Admin brandon profile Posts: 677

Every SQLStreams error carries a stable SQL code. The code renders at the end of the one-liner ([SQL0005]), in JSON logs, and in the CLI’s error block; paste the message text or code into search to land on its page.

CodeProblemRecovery
SQL0001instance is already consumingpermanent
SQL0002lifecycle context can never be cancelledpermanent
SQL0003lease lost to another consumerpermanent
SQL0004stream partition size does not match the existing streampermanent
SQL0005stream not foundpermanent
SQL0006stream still holds messagespermanent
SQL0007stream name already takenpermanent
SQL0008destroy is disabledpermanent
SQL0009stream name uses the reserved __system. prefixpermanent
SQL0010a worker instance is still livepermanent
SQL0011streams are still registeredpermanent
SQL0012worker instance row expired or was removedpermanent
SQL0013schedule not foundpermanent
SQL0014consumer group not foundpermanent
SQL0015consumer group still has a live consumerpermanent
SQL0016consumer group still has delivery rowspermanent
SQL0017system not registeredpermanent
SQL0018could not create the covering partitiontransient
SQL0019commit confirmation was lostpermanent
SQL0020stream partitions remain after drainingpermanent
SQL0021could not finish the stream declarationtransient
SQL0022schema version is older than this build requirespermanent
SQL0023schema version is newer than this build understandspermanent
SQL0024could not finish the worker declarationtransient
SQL0025could not finish the schedule declarationtransient
SQL0053could not take a lock needed by the migration steptransient
SQL0056partition creation cannot keep up with the id sequencepermanent

Log events share the same SQL code space: a Warn- or Error-level line that is operator-actionable carries its code in the line’s code attribute, and the code lands on a page here the same way.

CodeEventLevel
SQL0026lease reclaimed from expired workerwarn
SQL0027range quarantined after max reclaimswarn
SQL0028messages dead-letteredwarn
SQL0029message dead-letteredwarn
SQL0030exception dead-letteredwarn
SQL0031crash-loop kill backstop firedwarn
SQL0032stored message options outside this consumer’s boundswarn
SQL0033could not create partition aheadwarn
SQL0057no partition covers the next message idwarn
SQL0058schedule target stream keeps no success rowswarn
SQL0034worker instance lostwarn
SQL0035manager row suspendedwarn
SQL0036worker tick backoff curve exhaustederror
SQL0037schedule message was already produced by an earlier ambiguous commitwarn
SQL0038produce exceeded the duration thresholdwarn
SQL0039delivery dispatch exceeded the duration thresholdwarn
SQL0040worker tick exceeded its poll ratewarn
SQL0041consumer stoppedinfo
SQL0052abandoned-routine events droppedwarn
SQL0065system manager stoppederror

Declared metrics share the code space too: a measurement’s name resolves to its declaration, and sqlstreams explain accepts the code, the full name, or the stop-line attribute key (ready_count).

CodeMetricKind
SQL0042sqlstreams.consumer.session.claimedcounter
SQL0043sqlstreams.consumer.session.successcounter
SQL0044sqlstreams.consumer.session.supersededcounter
SQL0045sqlstreams.consumer.session.readycounter
SQL0046sqlstreams.consumer.session.deferredcounter
SQL0047sqlstreams.consumer.session.deadcounter
SQL0048sqlstreams.consumer.session.reclaimedcounter
SQL0049sqlstreams.consumer.session.quarantinedcounter
SQL0050sqlstreams.consumer.session.abandonedcounter
SQL0051sqlstreams.consumer.session.lease_lostcounter