schedule message was already produced by an earlier ambiguous commit [SQL0037]

code SQL0037 · log event at warn — degraded but self-healing, or a durable data consequence; an operator should learn of it eventually

the log line

· Report this thread

SQL0037 Log event at warn

As it arrives in your log:

level=WARN msg="schedule message was already produced by an earlier ambiguous commit" code=SQL0037

A schedule producer tick found its message already in the stream: an earlier tick’s commit confirmation was lost after the produce landed, so this tick produced nothing. The idempotency key made the retry safe; the schedule’s message does not land twice.

Landed here from a log? Paste the line — the queries above fill with your own values.

Nothing pasted yet — the queries above show their blanks.

Looking for a different code? Search every thread.

Jump to: