Execution search says it searches commands but never can – filters are client-side over one page #16

New Issue

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

jared commented

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

Overview

The search box placeholder promises "Search by command, execution ID, or workflow name". renderFilteredExecutions() tries to read e.logs[0].command, but the list endpoint does not return logs, so command search silently never matches. All filtering happens over the ≤50 rows currently loaded, while the server already implements search, status, workflow_id, started_by, after, before. The "Showing X of Y executions" stat is therefore also only about the loaded page.

Suggested fix

Send filters to the server (debounced), have the server search the first command_sent entry, and reset pagination on filter change. Add date-range inputs since the API supports them.

## Overview The search box placeholder promises "Search by command, execution ID, or workflow name". `renderFilteredExecutions()` tries to read `e.logs[0].command`, but the list endpoint does not return `logs`, so command search silently never matches. All filtering happens over the ≤50 rows currently loaded, while the server already implements `search`, `status`, `workflow_id`, `started_by`, `after`, `before`. The "Showing X of Y executions" stat is therefore also only about the loaded page. ## Suggested fix Send filters to the server (debounced), have the server search the first `command_sent` entry, and reset pagination on filter change. Add date-range inputs since the API supports them.

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

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#16