GitHub Actions UI/CLI shows jobs as "in progress" after being cancelled by concurrency setting

[noname0443]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

Hello! It seems like I've found a bug related to the concurrency setting in GitHub Actions.

I'm using this configuration:

concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref }}
  cancel-in-progress: true

I submitted a PR that uses this concurrency setting to cancel jobs on a commit push.

Here is how I encountered the bug:

• I pushed an initial commit to the PR, which started the GitHub Actions jobs.
• While those jobs were still running, I pushed a new commit to the same PR.
• The concurrency setting correctly and immediately canceled the jobs that were in a "queued" state.
• However, the jobs that were already in a "in progress" state did not cancel. Instead, they are now stuck. They hang with a "in progress" status and have already exceeded the GitHub Actions timeout (6h).

Here is what I'm seeing:

CLI:

$ gh run view --job 52715168817

X optimize_test_process_in_case_of_cancellation Docker tests (5.7) yandex/mysync#215 · 18500068871
Triggered via pull_request about 3 days ago

* test (GODOG_FEATURE=offline_mode.feature make test) in 0s (ID 52715168817)

ANNOTATIONS
X Canceling since a higher priority waiting request for Docker tests (5.7)-optimize_test_process_in_case_of_cancellation exists
test (GODOG_FEATURE=offline_mode.feature make test): .github#1


To see the full job log, try: gh run view --log --job=52715168817
View this run on GitHub: https://github.com/yandex/mysync/actions/runs/18500068871

$  gh run view --log --job=52715168817
job 52715168817 is still in progress; logs will be available when it is complete

At the same time, I do not see any real effect on the repository:

• The repository still has 20 available runners (the GitHub open-source limit).
• Usage metrics haven't changed for the past two days.

In my opinion, it seems like a concerning visual bug where the "canceled" jobs are not being properly terminated in the UI or system.

I'm not sure whether the full configuration is helpful, so you can check it in the PR.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐