Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
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.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
Hello GitHub Community,
I am experiencing a GitHub Actions workflow run that appears to be stuck in an inconsistent backend state.
Repository:
Private repository: aung1398/takara-erp
Workflow:
Secret scan (PR-CRED-1 control)
Workflow Run:
#326
Run ID:
32985126617
Pull Request:
#29
Current PR head SHA:
ecb3c0203da5502a943ca7b01abe66f24ea70d4c
The workflow run has remained stuck for approximately 3 days.
The workflow uses a GitHub-hosted runner:
runs-on: ubuntu-latest
The Actions UI showed:
The UI then displayed:
"An unexpected error has occurred and we've been automatically notified. Errors are sometimes temporary, so please try again."
Request ID shown by GitHub:
9020:31BF78:61F0DF:1480309:6A8F04BC
The run now appears to be in an inconsistent state:
The GitHub Actions UI displayed the unexpected-error annotation.
The Actions API continued to report Run #326 as:
status: queued
conclusion: null
The jobs API returned zero jobs for the run.
The GitHub UI does not show a "Cancel workflow" option.
An attempt to re-run the job through the GitHub API was rejected with HTTP 403:
"The workflow run containing this job is already running."
This is a GitHub-hosted ubuntu-latest runner, not a self-hosted runner.
The pull_request trigger does not have paths or paths-ignore filters that would explain the run being skipped.
I do not want to create an empty commit, modify the PR, or create duplicate workflow runs merely to work around a potentially stuck backend state.
Questions:
Is there a supported way to force this run into a terminal/cancelled state when the UI does not provide "Cancel workflow"?
Can GitHub staff investigate or clear the backend state for Run ID 32985126617 using the Request ID above?
Once the stuck run reaches a terminal state, is it safe to re-run the Secret Scan exactly once for the same PR head SHA?
Thank you.
All reactions