Route jobs
Monitor runs
Follow jobs across providers, inspect routing decisions, and open their logs in GitHub.
Runs brings your jobs’ execution history together across providers. Use it to see where a job ran, understand a fallback decision, or compare the results of a provider experiment.
Find your run
Select the repository’s GitHub account in the dashboard, then open Runs. Find the workflow and expand it to see its jobs. If it is missing, check the selected account and the App’s repository access in Settings.
Mirage receives workflow activity after the GitHub App is connected. Connect all repositories you want to monitor; enabling Mirage execution is a separate choice.
Read the result
Open a job to see its result, runner provider, available timing information, and machine assignment. The route reason explains why Mirage used your machine or a fallback. Expand the job’s steps to see progress and step timings.
| What you see | What it means |
|---|---|
| GitHub on attempt 1 | The job used a GitHub-hosted runner as its normal route. |
| Local infrastructure on attempt 1 | The job was routed to your connected machines. |
| Cloudflare | The job ran on the selected shared or BYO Cloudflare account. |
| GitHub on a later attempt | The job used the hosted label after fallback or a manual rerun. |
| A failed build or test | Open the step logs in GitHub to diagnose the application failure. |
| Queued or unavailable | Check the route reason, repository setup, and machine readiness. |
Attempt numbers belong to GitHub’s workflow run. Fallback keeps the same run ID and adds a new attempt.
For an onboarded job, open its provider comparison to see each experiment’s result and available capacity-wait, startup, and execution timings. Follow Compare CI providers to evaluate a different default route.
Logs and artifacts
Follow the run or job’s GitHub link for full step output and downloadable artifacts. GitHub remains the source of truth for checks and CI results. Mirage keeps routing, status, and timing information so you can understand execution without copying your full CI logs into another service.
For host setup failures, use the machine’s status and host diagnostics. Host diagnostics describe runner preparation and connection problems; they are separate from your test logs.
Actions billing estimates
The Billing page estimates monthly GitHub Actions usage for the selected account using observed jobs. It includes repositories shared with the App even if they do not use Mirage runners. Tracking starts when Mirage receives those repositories’ job events, so earlier activity may be missing.
Treat this as an estimate of GitHub Actions spend, not an invoice or a Mirage service price. Check GitHub for your actual charges and Cloudflare for usage billed to your own Cloudflare account.