My Github Actions is Queued for 2 hours

[yohan-koon]

Select Topic Area

Question

Body

I had to face this issue, when I tried to run github actions, when it triggers, the job is not starting for hours, it shows as queued and the github actions logs shows as below,

Requested labels: ubuntu-latest
Job defined at:
Waiting for a runner to pick up this job...

Can anyone help me to solve this issue? Please note, these pipelines worked well 1 day ago.

Here is my pipeline deployment code,

`name: Deploy to AWS

on:
push:
branches:
- master
- release/staging/*
- release/production/*

jobs:
deploy:
runs-on: ubuntu-latest

steps:
- name: Checkout code
  uses: actions/checkout@v2

- name: Set up Node.js
  uses: actions/setup-node@v2
  with:
    node-version: 20.x

- name: Install dependencies
  run: yarn install --frozen-lockfile

- name: Deploy to Dev
  if: github.ref == 'refs/heads/master'
  run: npx serverless deploy --stage dev
  env:
    AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
    AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

- name: Deploy to Staging
  if: startsWith(github.ref, 'refs/heads/release/staging/')
  run: npx serverless deploy --stage staging
  env:
    AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
    AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

- name: Deploy to Production
  if: startsWith(github.ref, 'refs/heads/release/production/')
  run: npx serverless deploy --stage production
  env:
    AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
    AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}`

[GamesmenJordan]

There is an outage, see githubstatus.com

[yohan-koon]

Noted @GamesmenJordan , Thanks

[alstp123]

We received a notice that the system has been restored to normal, but the workflows that were initiated during the issue remain in a queued state and are not being canceled. I'm not sure how to resolve this.

[satyagupte]

push a dummy commit and trigger a new run

[TengriKut1923]

I'm having the same problem. It was because of yesterday's outage. In the past, this problem was resolved within 24 hours.
https://github.com/orgs/community/discussions/49074

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬