The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-5vxb5 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-t8z4d lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-z8957 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-dbjzd lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-wpmfc lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-rpxm9 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-zr4gm lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-s8w75 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-z4m2z lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-jsf6c lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-xqzsq lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-lg6tq lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-2pwhd lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-2xpnd lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-6zh7m lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The self-hosted runner: windows-amd64-cpu4-qn6mp-runner-9bclm lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.