no partition covers the next message id [SQL0057]
Edit this pagecode SQL0057 · log event at warn — degraded but self-healing, or a durable data consequence; an operator should learn of it eventually
the log line
As it arrives in your log:
level=WARN msg="no partition covers the next message id" code=SQL0057
An insert was routed to a message_log partition that did not exist, and the write path created it. Nothing is lost — the attempt reruns on the retry schedule (SQL0056) — but that insert paid the creation latency instead of the create-ahead pass.
Once at a boundary means create-ahead did not run: no consumer is
running the stream’s upkeep. Every boundary under load means bursts are
outrunning the 80% and 95% triggers: raise PartitionSize.
Nothing pasted yet — the queries above show their blanks.
Looking for a different code? Search every thread.