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: ultramarine-linux-deployment-sqmc8-bqc9j 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 operation was canceled.

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

The operation was canceled.

The self-hosted runner: ultramarine-linux-deployment-sqmc8-2zzgt 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 operation was canceled.

Process completed with exit code 1.

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: ultramarine-linux-deployment-sqmc8-qq2xn 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.