{
  "id": 13578829,
  "title": "FAQ: A Drafted Retry Block Is Not a Flake Policy",
  "url": "https://urgent.news/2026/10/10/faq-a-drafted-retry-block-is-not-a-flake-policy",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-10T23:31:05.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/gitlab_3188/faq-a-drafted-retry-block-is-not-a-flake-policy-3bi6"
  },
  "original_language": "en",
  "account": "A retry block in GitLab CI is not a replacement for addressing flaky jobs. When someone adds a retry key, it only queues another attempt to run the job, not guaranteeing stability. The myth claims that the retry key makes the job safe, but evidence shows it only spends a failure budget. The network blip, cold cache warming, or other minor issues could cause a passing second attempt, leaving the underlying bug unchanged. GitLab documents retry as rerun control, not a diagnosis.",
  "summary": "A red job came back green after a single retry. Someone pasted a model draft and called the flake gone. I do not buy that story without a real job log. The YAML looked tidy, and the chat looked confident. The pipeline contract was still missing from the diff. Have you merged a draft like that in the last month? Why this FAQ exists I review GitLab CI drafts more often than application code. People…",
  "key_points": [
    "Retry block in GitLab CI does not replace flaky job fixes.",
    "Retry key queues another job attempt, not job stability guarantee.",
    "Myth suggests retry key makes job safe, but only spends failure budget."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}