Troubleshooting

This page collects the most common issues teams hit when setting up Tenki Runners, along with the fastest way to resolve each one. If you're still blocked after working through the relevant section, we're one email away.

My organization isn't showing up in Tenki

Not seeing your organization in the Tenki dashboard? Here are a few things to check:

• The Tenki GitHub App isn't installed on your GitHub Organization. Make sure it's properly installed. (Settings > Applications > Installed GitHub Apps)
• Your GitHub user isn't a member of the organization. Double-check your access.
• If you selected Only select repositories during installation: Make sure you’re pushing to a repository that’s actually included in your selection. If not, you can update the list anytime from your GitHub settings. See Manage your GitHub Repositories for how access stays in sync.

My jobs are stuck as "queued" or never start

When a job stays queued and never picks up a Tenki runner, it's almost always a label or capacity issue:

• The runs-on label doesn't match a Tenki runner. Confirm your workflow targets a valid Tenki label (for example tenki-standard-small-2c-4g). See Which runner should I use? for the full list of available sizes.
• You've hit your plan's concurrency limit. Jobs above your concurrent-job ceiling wait for a free slot. Review Limits & Concurrency to see your current limits and how to raise them.
• GitHub Actions is disabled for the repository. Check Settings → Actions → General and ensure Actions are allowed.

My build runs out of memory or is slower than expected

• If a job is killed or thrashes, it likely needs a larger runner. Pick a size with more vCPU/RAM. See Which runner should I use? and Linux x64 Runners.
• First-run cold starts and cache behavior are covered in Limits & Concurrency. Warm caches significantly reduce repeat-build times.

Frequently asked questions

Do I need to change my workflow files to use Tenki? No. Tenki is a drop-in replacement for GitHub-hosted runners; you only change the runs-on value. Everything else in your workflow stays the same.

Will switching runner size break my pipeline? No. Runner size only affects the compute allocated to the job; your steps and commands are unchanged.

A repository is missing from Tenki. What do I do? Confirm the repo is included in the Tenki GitHub App's repository access list. Changes you make in GitHub sync automatically. See Manage your GitHub Repositories.

Still stuck? Reach out to us at hello@tenki.cloud and we'll be happy to help.