fix: back off after ops claim errors
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02b6f-7db1-7222-918b-e813a6bda38d
This commit is contained in:
parent
81d6222c6b
commit
db588010f7
3 changed files with 37 additions and 4 deletions
|
|
@ -106,3 +106,11 @@ deployment rsync now excludes `.venv`, preventing workstation-bound shebangs
|
|||
from overwriting the live worker environment. railiance01 is healthy on the
|
||||
legacy worker but still needs the Glas checkout/package install, deployment,
|
||||
restart, and coordinated pilot.
|
||||
|
||||
Deployment then exposed a pre-existing upstream database mismatch: the live
|
||||
Activity Core image selects `ops_runs.harness_profile_ref`, but production
|
||||
PostgreSQL has not applied migration `0008`, so every claim returns 500. The
|
||||
worker's prior error path retried that failure every two seconds; it now uses
|
||||
the configured 30-second backoff for claim errors and reserves the short pause
|
||||
for cycles that actually claimed work. Activity Core must apply/verify its
|
||||
migration before the coordinated pilot can run.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue