Multi-target execution is sequential (quick command and workflow steps) #26

New Issue

2026-09-08T20:57:30-04:00

jared commented

2026-09-08 20:57:30 -04:00

Overview

Workflow execute steps with targets: ['all'] send the command to one worker, await its result (up to the step timeout), then move to the next worker. With 10 workers and a 2-minute step timeout a single hung worker delays the step by minutes and total time scales linearly. README advertises running commands "across multiple worker nodes simultaneously".
Multi-worker Quick Command likewise POSTs to each worker one after another.

Suggested fix

Send to all targets first, then Promise.allSettled the results; report per-worker outcome in one log entry; optionally add parallel: false per step for ordered rollouts. Add a batch endpoint (POST /api/commands with worker_ids[]) for the UI.

## Overview - Workflow `execute` steps with `targets: ['all']` send the command to one worker, `await` its result (up to the step timeout), then move to the next worker. With 10 workers and a 2-minute step timeout a single hung worker delays the step by minutes and total time scales linearly. README advertises running commands "across multiple worker nodes simultaneously". - Multi-worker Quick Command likewise POSTs to each worker one after another. ## Suggested fix Send to all targets first, then `Promise.allSettled` the results; report per-worker outcome in one log entry; optionally add `parallel: false` per step for ordered rollouts. Add a batch endpoint (`POST /api/commands` with `worker_ids[]`) for the UI.

jared added the enhancement frontend backend workflow-engine priority/medium labels 2026-09-08 20:57:30 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#26