fix(backend): stop different tasks' queued runs from silently merging (#3517)
Co-authored-by: nova28 <17953305+nova28@users.noreply.github.com> Co-authored-by: Carlos Florencio <carlosmflorencio@gmail.com>
This commit is contained in:
@@ -184,12 +184,15 @@ A reviewer rejecting a Review:
|
||||
|
||||
`office_runs` is renamed `runs`. Universal queue for engine-emitted
|
||||
launches. Every `queue_run` action creates a row. Coalescing (5s
|
||||
window for same agent + reason), idempotency (a 24h lookup plus a durable
|
||||
window for same agent, reason, and task bucket), idempotency (a 24h lookup plus a durable
|
||||
unique key),
|
||||
per-agent serialisation (one claimed run per agent), cooldown
|
||||
(per-agent, default 10s), and atomic task checkout (one agent per
|
||||
task at a time) all apply — same machinery as today's office_runs.
|
||||
|
||||
A task bucket is the nonempty `task_id`. Missing, null, or empty
|
||||
`task_id` values use the taskless bucket.
|
||||
|
||||
User-initiated launches (clicking Start on a kanban task) bypass the
|
||||
queue and call `runtime.Launch` directly — those don't need
|
||||
coalescing and shouldn't pay the scheduler's tick latency.
|
||||
|
||||
Reference in New Issue
Block a user