Troubleshooting
Auto-retry rule not firing
A retry rule exists but the failed job was not retried — scope, conclusion-type, and attempt-limit checks.
Work through these in order:
- Scope mismatch — the rule's repository, workflow, branch, and job name filters must all match the failed run. A rule scoped to
ci.ymlignores failures indeploy.yml, and a job filter only matches when that exact job name failed. - Conclusion type not selected — rules fire only on the conclusion types you checked.
failureis the default; atimed_outorcancelledrun is not retried unless you added it. - Attempts exhausted — after the configured maximum (1–3), Gitera stops retrying that run; the history shows
Failed permanently. - Rule limit reached — rules over your plan's limit cannot be created; check the count on the Auto-retry page.
- Timing — rules apply to failures after creation; past failures are not retried retroactively.
The history & audit log on the Auto-retry page lists every retry event — if the run never appears there, the rule never matched (scope or conclusion type); if it appears with Failed permanently, the retries ran but the error is not transient.