Troubleshooting

Learn how to solve the most common issues you may encounter during setup or on GitHub workflow summaries:

• The run was canceled by @sprinters-sh[bot].
• The self-hosted runner: i-0123456789abcdef0 lost communication with the server.
• I want to run jobs from multiple GitHub accounts onto the same AWS account.

The run was canceled by @sprinters-sh[bot].

There was a problem launching an instance in your AWS account. GitHub unfortunately doesn’t permit external tools to post additional details in the workflow summary.

In the Sprinters Console, the workflow run will show the exact cause of the error and how to fix it.

The self-hosted runner: i-0123456789abcdef0 lost communication with the server.

When using spot instances, AWS will sometimes reclaim them when EC2 is short on capacity. This message indicates that this runner instance was terminated because of this and that eventually GitHub Actions took notice it was no longer available.

In the Sprinters Console, the workflow run will show the exact cause of the error and how to fix it.

I want to run jobs from multiple GitHub accounts onto the same AWS account.

To the run jobs from multiple GitHub accounts onto the same AWS account, simply adjust the IAM role trust policy to include a list of GitHub accounts instead of a single one:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "381491863103"
            },
            "Action": "sts:AssumeRole",
            "Condition": {
                "StringEquals": {
                    "sts:ExternalId": [
                        "first-github-account-name",
                        "second-github-account-name",
                        "yet-another-github-account-name"
                    ]
                }
            }
        }
    ]
}