how to run GitHub Action after outage?

Question

As you may (or may not) know yesterday was a major incident of GitHub's services: https://www.githubstatus.com/incidents/tyc8wpsgr2r8.

Unfortunately I published a release during that time and the action responsible for building and publishing the code didn't trigger.

For actions which were executed at least once I have an option to "Re-run workflow" - but how can I proceed with an action which didn't even trigger - I can not see it anywhere whatsoever?

I think the last resort would be to just make another release, remove the problematic one etc. but I'd like to avoid that.

The workflow file:

name: Node.js CI

on:
  push:
    branches: [master]
  release:
    types: [published]
  pull_request:
    branches: [master]
jobs:
  test:
    name: Test Node.js v${{ matrix.node-version }}
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version:
          - 16
    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v2
        with:
          node-version: ${{ matrix.node-version }}
      - run: npm install --production=false --no-package-lock
      - name: Lint 💅🏻
        run: npm run lint
      - run: npm test
  release:
    name: Publish NPM Package
    if: startsWith(github.ref, 'refs/tags/')
    needs:
      - test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16
          registry-url: 'https://registry.npmjs.org'
      - run: npm install --production=false --no-package-lock
      - run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
  gh-pages:
    name: Publish GitHub Pages
    if: ${{ github.ref == 'refs/heads/master' || github.ref == 'refs/heads/main' }}
    needs:
      - test
    runs-on: ubuntu-latest
    continue-on-error: true
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16
          registry-url: 'https://registry.npmjs.org'
      - name: Install ✔️
        run: npm install --production=false --no-package-lock
      - name: Build storybook 🏗️
        run: npm run build-storybook
      - name: Deploy 🚀
        uses: JamesIves/[email protected]
        with:
          branch: gh-pages
          folder: storybook-static

Answer 1

As you said in the comment, the easiest solution would be to remove the release and create it all over again.

Another option could be to add a workflow_dispatch event trigger to the workflow with a tag input, updating the jobs condition to use this input.tag variable if informed.

That way, if an automatic trigger failed (through push, release or pull_request), you could trigger it manually through the Github UI or the GH CLI as an alternative.