GiteraGitera Docs
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:

  1. Scope mismatch — the rule's repository, workflow, branch, and job name filters must all match the failed run. A rule scoped to ci.yml ignores failures in deploy.yml, and a job filter only matches when that exact job name failed.
  2. Conclusion type not selected — rules fire only on the conclusion types you checked. failure is the default; a timed_out or cancelled run is not retried unless you added it.
  3. Attempts exhausted — after the configured maximum (1–3), Gitera stops retrying that run; the history shows Failed permanently.
  4. Rule limit reached — rules over your plan's limit cannot be created; check the count on the Auto-retry page.
  5. 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.