Pipeline System Error: Runner currently has no pipeline scheduled.

[Sena Turku Cakmak]

Hello,

Our pipeline keeps giving system error in the middle of a step, after completing couple of other steps. All the pushes right now ends with a System error. I have followed troubleshooting document that was provided by Atlassian, but the error I see isn't included in the document. what I see is:

"

An error occurred whilst updating step progress.
com.atlassian.pipelines.stargate.client.core.exceptions.StargateForbiddenException: Response Summary:

HttpResponseSummary{httpStatusCode=403, httpStatusMessage=Forbidden, bodyAsString={"error":{"message":"Forbidden","detail":"Runner currently has no pipeline scheduled.","data":{"key":"rest-service.rest-service.forbidden","arguments":{}}}}}

"

I am not sure how to proceed, I would appreciate any help.

Thanks,

Sena

[Theodora Boudale]

Hi Sena,

The error you posted here seems to be coming from a self-hosted runner's log.

I would like to ask a few questions so I can better help you:

1. What type of runner are you using for these failed steps? Linux Docker (x86_64), Linux Docker (arm64), Windows, MacOS or Linux Shell runners?
   
   
2. Are you using the latest version of the runner? You can see that in the build log of a step that didn't fail with this error, in the section Runner.
   
   
3. Is the runner running in one of the supported platforms mentioned here? https://support.atlassian.com/bitbucket-cloud/docs/runners/#Supported-platforms
   
   
4. Was the runner working before or is this a new setup that never worked?
   
   
5. Do you have multiple runners running on the same machine?
   
   
6. Are you perhaps using the preconfigured command to start a runner multiple times? Please keep in mind that a single command can be used to start only one instance of a runner, as it contains unique OAuth credentials. If you use it multiple times, it can cause conflicts.
   
   
7. Does the machine where the runner is executing go to "Sleep" mode after some time? This can cause the runner to lose the connection to Bitbucket infrastructure.

Kind regards,
Theodora