We were unable to run this job. Please check your configuration and try again.

If you have a build fail with the error message "We were unable to run this job. Please check your configuration and try again." it could be from a few sources.

Screen_Shot_2021-11-01_at_12.03.48_PM.png

Active Incident

This error can occur if we are currently having an issue with the CircleCI service, so if you are getting this error and there is a current active incident that is the likely cause:

https://status.circleci.com/

However, if you need confirmation feel free to reach out to the support team to confirm that is the root cause.

Error from GitHub checks API endpoint

If you are utilizing status checks with your CircleCI workflows, we continually send API calls to GitHub to report the status of your workflow as it progresses. However, the GitHub checks API endpoint has a 65535 character limit on the output key:

https://github.com/github/docs/issues/3765

With the above, if you have a large number of jobs in your workflow -- or very long job names -- you may hit this character limit. If you do, you'll see the above-mentioned error, and if you need confirmation you can reach out to the support team.

For each job, a status check is made, and the job name is included and contributes to the character limit. One way to work around this error is to consolidate jobs, or shorten job names, to be below the character limit.

Another option would be to utilize parallelism where you can run multiple containers in a single job, as only a single check will be made of that job.

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.