Troubleshooting

Having trouble with Blaze? Here are some common issues and how to fix them.

Stuck at "Waiting for runner"

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

  • Have you added your organization / account to the Allowlist in the Blaze dashboard? - Check here
  • Is the Blaze GitHub App installed on your GitHub account? - Check here
  • Does Blaze have access to your repository? - Check here
  • Are you using the correct runner tag in your workflow config? - Check here
  • If its a public repo, have you allowed the Default runner group access to public repositories?
    Org Settings > Actions > Runner groups > Default > Edit
  • Are you running more jobs than you have runners? Consider getting more runners. Pricing info here
  • Restart the workflow run

If you've checked all these things, and you're still getting "Waiting for runner", please uninstall the Blaze GitHub Application and then re-install it again. If you're still experiencing issues after following these steps, please get in touch with support at contact@runblaze.dev.

GitHub Actions Cache is slow

This is because of an issue inside GitHub's internal CDN. We recommend using a third party caching solution such as buildjet/cache. We hope Github is able to resolve this issue soon.

Other issues

If your issue isn't listed here or you're still experiencing issues after following the recommendations on this page, please contact support at contact@runblaze.dev. Please make sure to include all relevant information such as the workflow run URL in your message, so we can lookup the workflow run ID.