Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

Relationships

#992 Worker fleets phase 6: raise default queue timeout to 10 minutes

Opened by stack72 · 7/6/2026· Shipped 7/6/2026

Summary

Phase 1 shipped a conservative 60-second default queue timeout so that the behavior change (queue-on-empty instead of fail-fast) would surface misconfigurations quickly. Now that fleets, lifecycle, verification, and capacity slots are all in place, raise the default to 10 minutes to match realistic cold-start times for autoscaled fleets (ASG scale-up, k8s scale-from-zero).

Users already have full visibility into the queue (`step_queued` events, `swamp worker queue`), per-step `queueTimeout` overrides, and `--queue-timeout` on serve. The 10-minute ceiling is the right default for production fleets.

Design reference: `worker-fleets.md` section "Phase 6 — Production queue timeout".

Changes

Two lines:

  1. `src/serve/dispatch_service.ts`: Change `DEFAULT_QUEUE_TIMEOUT_MS` from `60 * 1000` to `600 * 1000`

  2. `src/cli/commands/serve.ts`: Update the `--queue-timeout` help text default display from `60s` to `10m`

Tests

Update any unit or integration tests that assert on the default timeout value. The dispatch service test at `src/serve/dispatch_service_test.ts` uses explicit `queueTimeoutMs` overrides in most tests, so only tests relying on the default need updating.

Acceptance criteria

  1. `swamp serve` with no `--queue-timeout` flag waits up to 10 minutes for a matching worker
  2. `--queue-timeout 60s` still overrides to 60 seconds
  3. Per-step `queueTimeout: 30` still overrides both
  4. All existing tests pass
  5. `deno check`, `deno lint`, `deno fmt`, `deno run test`, `deno run compile` all pass
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 4 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

7/6/2026, 9:00:11 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack727/6/2026, 8:15:22 PM

Sign in to post a ripple.