Execution list items don't show the command or worker for quick commands #15

New Issue

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

jared commented

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

Overview

Every quick/scheduled/internal execution is listed as [Quick Command] with only the user and time. Twenty rows of [Quick Command] are indistinguishable without opening each modal. The detail modal likewise shows Worker ID: <uuid> rather than the worker name.

Multi-worker quick commands create N unrelated executions with no grouping key, so results for one action are scattered across the list.

Suggested fix

Have GET /api/executions return a short summary (first command, truncated) and worker_name(s) via a join / JSON_EXTRACT(logs,'$[0].command').
Render df -h @ pulse-worker-01 in the row.
Add a batch_id to executions created by one multi-worker submission and group them visually.
Resolve worker ids to names in formatLogEntry.

## Overview Every quick/scheduled/internal execution is listed as `[Quick Command]` with only the user and time. Twenty rows of `[Quick Command]` are indistinguishable without opening each modal. The detail modal likewise shows `Worker ID: <uuid>` rather than the worker name. Multi-worker quick commands create N unrelated executions with no grouping key, so results for one action are scattered across the list. ## Suggested fix - Have `GET /api/executions` return a short `summary` (first command, truncated) and `worker_name`(s) via a join / `JSON_EXTRACT(logs,'$[0].command')`. - Render `df -h @ pulse-worker-01` in the row. - Add a `batch_id` to executions created by one multi-worker submission and group them visually. - Resolve worker ids to names in `formatLogEntry`.

jared added the enhancement ux frontend backend executions priority/medium labels 2026-09-08 20:57:24 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#15