Replies: 5 comments
|
Same too... |
0 replies
|
Me too |
0 replies
|
Same |
0 replies
|
Any update? My actions are still stuck, and still cannot be cancelled |
0 replies
|
All seems to be working by now; got some queued actions but after pushing new commits - new actions started working |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
Summary
A workflow run remains
in_progressin both the GitHub UI and REST API even though all steps in its final job have finished, including post-action cleanup andComplete job.Attempting to cancel the run through the GitHub UI returns:
During the same period, another workflow remained queued without any jobs being created, and an independent CodeQL workflow ended with
startup_failure, also with zero jobs.Environment
OpmanAI/edge— privatestagingubuntu-latest43093759469130777539925Run URL:
https://github.com/OpmanAI/edge/actions/runs/43093759469
The repository is private, so the run and logs may not be publicly accessible.
What happened
Setup Supabase CLIstep stopped producing output insidebun src/main.ts.cancelledand subsequent deployment steps asskipped.Complete jobfinished successfully.in_progress.We have not established whether the initial setup-step stall and the subsequent workflow finalization issue share the same cause.
Timeline
All times are UTC on November 11, 2026.
cancelledskippedComplete jobcompleted successfullyin_progressREST API evidence
Workflow run
Request:
Relevant response fields:
{ "id": 43093759469, "status": "in_progress", "conclusion": null, "run_attempt": 1, "created_at": "2026-11-11T20:08:57Z", "updated_at": "2026-11-11T20:20:40Z" }Deployment job
Request:
Relevant fields for the final job:
{ "id": 130777539925, "name": "Deploy to Staging", "status": "in_progress", "conclusion": null, "completed_at": null, "runner_name": "GitHub Actions 1000009829" }However, every step in that job was already marked completed:
Job log retrieval
Request:
Response:
{ "message": "Server Error" }Response headers included:
Other affected runs during the same period
Staging Pipeline #537
https://github.com/OpmanAI/edge/actions/runs/43095819678
20:24:03 UTCqueued{ "total_count": 0, "jobs": [] }CodeQL #275
https://github.com/OpmanAI/edge/actions/runs/43095818433
20:24:02 UTCcompletedstartup_failure20:36:29 UTC{ "total_count": 0, "jobs": [] }Previous staging and CodeQL runs had completed successfully.
These observations are included as potentially related context, not as proof that one workflow caused the others to fail.
Original stalled step
The action successfully completed Bun setup and dependency installation, then stopped producing output at:
After cancellation, the log displayed:
The workflow does not declare a
concurrencygroup.Expected behavior
Questions
in_progress?Screenshots showing the contradictory status and cancellation error are attached.
All reactions