Documentation
Troubleshooting
Check authorization and the runner label before changing workflow code.
Job stays queued
- Confirm the GitHub App selected in the installation guide is installed and active for the repository running the workflow.
- Confirm the workflow uses the eligible Linux x64 label shown in the portal.
- Confirm the workspace has available allowance and that no other job is running.
- Check the GitHub Actions run page for the job's queue message.
Runner is not eligible
A Runzivo label does not authorize a repository by itself. Check the GitHub App's selected-repository configuration in the portal, then reconnect the installation if it was recently changed.
A job fails after it starts
Read the GitHub Actions logs first. Compare the failing command with a known run and verify any environment secret, permission, or external dependency the workflow requires. Do not include secrets in support information.
CLI commands fail
See the CLI guide's own troubleshooting section for CLI-specific error messages.
Need help
Email support@runzivo.dev with the repository name, workflow run URL, job name, UTC time, and a redacted error excerpt. Do not send credentials or secret values.