Testing the agentspan CLI against a live 3.32.0-rc.9 server: conductor agent execution lists executions fine unfiltered and with --name, but every time filter returns nothing — even with executions created seconds earlier.
conductor agent execution # lists 50+ executions
conductor agent execution --since 1h # No executions found
conductor agent execution --since 1d # No executions found
conductor agent execution --window now-7d # No executions found
Tried all the documented formats (1h, 6h, 1d, 7d, now-7d) — every one comes back empty.
Root cause: the CLI builds freeText=startTime:[<ms> TO *], which the server's execution search (SQLite) doesn't honor. Confirmed against the raw endpoint:
/api/agent/executions?freeText=* → totalHits 69
/api/agent/executions?freeText=startTime:[<ms> TO *] → totalHits 0
So --since / --window silently match nothing, and a user reasonably concludes they have no recent executions.
Fix: internal/agent/client.go → buildExecutionFreeText. Either emit a query the server's search backend supports, or fall back to client-side time filtering.
Testing the agentspan CLI against a live 3.32.0-rc.9 server:
conductor agent executionlists executions fine unfiltered and with--name, but every time filter returns nothing — even with executions created seconds earlier.Tried all the documented formats (
1h,6h,1d,7d,now-7d) — every one comes back empty.Root cause: the CLI builds
freeText=startTime:[<ms> TO *], which the server's execution search (SQLite) doesn't honor. Confirmed against the raw endpoint:So
--since/--windowsilently match nothing, and a user reasonably concludes they have no recent executions.Fix:
internal/agent/client.go→buildExecutionFreeText. Either emit a query the server's search backend supports, or fall back to client-side time filtering.