schedule config replaced [SQL0062]
Edit this pageAs it arrives in your log — example values stand where yours will:
level=WARN msg="schedule config replaced" code=SQL0062 schema=sqlstreams schedule_id=3
Client.Scheduler(name).Register found the schedule already registered and the
declared config differed from the stored row. The row keeps the newest
declaration, and each changed config field rides the line as its own
attribute carrying old -> new. The payload and Metadata documents are
never logged: a changed one rides as payload_changed or
metadata_changed and nothing of what it holds. A changed cron expression also moves
next_scheduled_at: a run already due under the old expression is
dropped, not produced late, and the line carries the new
next_scheduled_at.
One line is a config change landing. The same line on every deploy
means two services both declare the schedule with different configs
and overwrite each other on restart - a schedule’s config wants exactly
one declaring service, and nothing in the library enforces that beyond
this line. schedule_config keeps no declaration trail the way
stream_config_log and worker_config_log do, so the diagnose query
shows the row as stored now; the earlier config values are only in the log
lines, and an earlier payload is nowhere:
sqlstreams explain SQL0062
Helpful info.
the schedule row as stored now (schedule_config keeps no declaration trail)
SELECT name, expression, concurrency, timeout_ns, suspended FROM {schema}.schedule_config WHERE id = {schedule_id};
Looking for a different code? Search every thread.