Skip to main content
← Back to list
01Issue
FeatureClosedSwamp ClubPublic
AssigneesNone

Relationships

#3199 Docs: concurrent scheduled runs and queue delay in swamp serve

Opened by stack72 · 10/8/2026

Follow-up to swamp-club#3046 (manual pages in content/manual).

  • reference/swamp-serve.md: document max-concurrent-scheduled-runs (config key), SWAMP_MAX_CONCURRENT_SCHEDULED_RUNS and --max-concurrent-scheduled-runs. Cover the default of 1 (one scheduled run at a time, as before) and how it differs from max-concurrent-runs, which limits API runs. Document the new per-schedule /health fields: queued, oldestQueuedAt and lastQueueDelayMs.
  • how-to/run-workflows-on-a-schedule.md: explain running schedules concurrently, that a workflow never overlaps itself (a fire while it runs is skipped; a fire while it is queued waits), how to read queue delay from /health or the dashboard, and that each run still pays its datastore sync time (see swamp-club#3198 for the S3 pull cost).
02Bog Flow
✓OPEN○TRIAGED○IN PROGRESS◉CLOSED

Closed

10/12/2026, 9:41:12 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

stack72 commented 10/12/2026, 9:41:12 PM

Documented in the manual by swamp-club/swamp-club#1324 (merged).

Sign in to post a ripple.