Pages workflow stuck in_progress with all jobs terminal; rerun denied as running and cancel denied as not running #210667
Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
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.
Public repository: https://github.com/2DPerformance/2DPerformance
Run: https://github.com/2DPerformance/2DPerformance/actions/runs/39280185653
Check suite: 106440868848
Pages commit: bdc87e220a40bd1153fa47ea940caae7745bb6bf
Affected deploy job: 118153224241
Retained github-pages artifact: 12200725872, 79,497,747 bytes, not expired
Artifact SHA256: 262d6f90488b8134e2d1c725e2c55f25276ccb0e72da57a01a655ddda6954cd1
Following incident https://www.githubstatus.com/incidents/8tzbpcnl75jp (resolved 2026-10-19T16:56:58Z), this run still reports in_progress / attempt1 / updated_at16:26:38Z. Authenticated REST, unauthenticated public REST and the browser agree. Fresh HTTP Date and different X-GitHub-Request-Id values rule out local response caching.
All actual jobs and check runs are terminal: build success, report-build-status success, deploy cancelled at16:01:34Z. There are no pending environment approvals. Deployment7178206861 became error at16:26:38Z. The expected recovery requested at16:23 did not materialize any new jobs.
Official Pages deployment cancel for the exact unpublished Pages commit returned204 at17:10, and its status is now deployment_cancelled; the Pages build changed to errored. This did not reconcile the workflow run aggregate.
One authorized recovery of the same deploy job was rejected:
POST actions/jobs/118153224241/rerun ->403 'The workflow run containing this job is already running'
Date 2026-10-19T17:14:05Z; request ID708C:3D8E6A:A8442C:FD7235:6AD64FDD
A failed-jobs-only route, verified to include only this cancelled deploy and no successful build job, was also rejected:
POST actions/runs/39280185653/rerun-failed-jobs ->403 'This workflow is already running'
Date 2026-10-19T17:17:35Z; request ID709E:1751DA:A83A05:FE56DC:6AD650AF
Normal cancel reports already completed. Force cancel and the official browser Cancel workflow button report not in progress. The browser simultaneously displays In progress. No new recovery job was accepted or created by these rejected requests.
Please repair/reconcile the existing workflow run state and enable resuming only its cancelled deploy job from the retained artifact. Do not delete the artifact, create a new publication commit, change Pages/CNAME/environment protections or rerun the successful build.
Live https://naichangyai.com/website-release.json still serves sourceCommit dee54354c23a6c98dc01b1f4dad7e9a3172271f0 / catalogVersion2026.10.19.17. The retained Pages commit/artifact contains target metadata sourceCommit748434d9299c0c9ef9d7b08c0e7f0feb25e708c1 / catalogVersion2026.10.19.18. These are metadata source IDs; bdc87e2 is the actual static Pages Git commit.
No credentials, access tokens, local project/model files, PDFs or customer data are included in this report.
All reactions