Troubleshooting

There are a couple of things you can do before contacting support.

• Is the BuildJet GitHub App installed on your GitHub account? - Check here
• Does Buildjet have access to your repository? - Check here
• Are you using the correct runner tag in your workflow config? - Check here
• Are you running more vCPUs than you're allowed? Read more about concurrency here

If you've checked all these things, and you're still getting "Waiting for runner", please uninstall the BuildJet GitHub Application and then re-install it again.

If that doesn't work, please contact our contact@buildjet.com.

Unfortunately, this is because of an issue inside GitHub's internal CDN. We recommend using the BuildJet cache, buildjet/cache, a reliable & fast alternative to GitHub's cache. It is compatible with any runner - official, self-hosted, or BuildJet, and no matter the runner in use, BuildJet provides 20 GB/month of storage space for free.

To get started with BuildJet cache, simply replace action/cache with buildjet/cache.

yaml
1
...
-
- uses: action/cache@v3
+
- uses: buildjet/cache@v3
4
  with:
5
    path: ~/.npm
6
    key: buildjet-node-${{ hashFiles('**/package-lock.json') }}
7
    restore-keys: |
8
      buildjet-node-
9
...

Read more about migrating to Buildjet Cache.