Re-run button on workflow executions re-runs only the first command as a quick command #18

New Issue

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

jared commented

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

Overview

viewExecution() shows 🔄 Re-run Command whenever any command_sent log entry exists – including workflow executions. Clicking it copies the first step's command into Quick Command targeting that worker, dropping the rest of the workflow, parameters and prompts. It also silently leaves the worker dropdown unchanged if that worker id is no longer listed, and never switches the mode back to "Single Worker".

Suggested fix

For workflow executions offer Re-run workflow (re-POST /api/executions with the same workflow_id and the params from the params log entry).
For quick commands keep the current behaviour but force single mode and validate the worker still exists (offer a picker otherwise).

## Overview `viewExecution()` shows **🔄 Re-run Command** whenever any `command_sent` log entry exists – including workflow executions. Clicking it copies the *first* step's command into Quick Command targeting that worker, dropping the rest of the workflow, parameters and prompts. It also silently leaves the worker dropdown unchanged if that worker id is no longer listed, and never switches the mode back to "Single Worker". ## Suggested fix - For workflow executions offer **Re-run workflow** (re-POST `/api/executions` with the same `workflow_id` and the `params` from the `params` log entry). - For quick commands keep the current behaviour but force single mode and validate the worker still exists (offer a picker otherwise).

jared added the bug ux frontend executions priority/medium labels 2026-09-08 20:57:26 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#18