fj workflow run: "could not find the triggered run" after every dispatch (server reports an empty event) #321

Closed
opened 2026-11-12 05:23:18 +00:00 by stephen · 0 comments
Owner

fj workflow run <wf> --ref <branch> dispatches the workflow, then fails after about 30 seconds with:

dispatched `ci.yml` on `<branch>`, but could not find the triggered run

The run does exist and starts normally.

Cause: after dispatching, fj polls the run list for a new run whose event is workflow_dispatch. The Forgejo on rasterhub.com reports an empty event for dispatched runs (its payload carries inputs and ref, but the event field is ""), so the filter never matches. Push runs report push and pull request runs report pull_request, so only dispatch runs are affected. It hits every dispatch, on any branch, including workflows that take their own ref input (the run is on the default branch there, which is correct).

Fix: accept an empty event as a dispatch candidate, keeping the workflow, branch and not-seen-before checks, and still reject runs that report another event.

`fj workflow run <wf> --ref <branch>` dispatches the workflow, then fails after about 30 seconds with: dispatched `ci.yml` on `<branch>`, but could not find the triggered run The run does exist and starts normally. Cause: after dispatching, fj polls the run list for a new run whose event is `workflow_dispatch`. The Forgejo on rasterhub.com reports an empty `event` for dispatched runs (its payload carries `inputs` and `ref`, but the `event` field is `""`), so the filter never matches. Push runs report `push` and pull request runs report `pull_request`, so only dispatch runs are affected. It hits every dispatch, on any branch, including workflows that take their own `ref` input (the run is on the default branch there, which is correct). Fix: accept an empty event as a dispatch candidate, keeping the workflow, branch and not-seen-before checks, and still reject runs that report another event.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rasterstate/fj#321
No description provided.