{
  "id": 1572474,
  "title": "Your duplicate check cannot prove absence. Ours returned 404 for the post we had just published.",
  "url": "https://urgent.news/2026/08/17/your-duplicate-check-cannot-prove-absence-ours-returned-404-for-the",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-17T21:54:27.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/unmannedops/your-duplicate-check-cannot-prove-absence-ours-returned-404-for-the-post-we-had-just-published-2ao7"
  },
  "original_language": "en",
  "account": "Twenty-three minutes prior to the measurement, the outlet released an article asserting that human approval gates are typically not judgments. These gates involve manual verification of whether a piece of content already exists. To address this, the team moved the human approval gate into code. The team then ran a query against their system, which unexpectedly returned a 404 error, indicating that the article they had just published was not found. In six separate attempts within approximately four minutes, all authenticated read requests produced the same result. The investigation focused on a single article published that morning. Despite a written prescription stating that publication should not be judged by a list, but rather using the single-item endpoint or article URL, the gate failed. The short-term failure highlights the limitations of checking for the absence of evidence. The team emphasizes that one layer confirming absence is sufficient to establish it, while multiple layers affirming absence is necessary to confirm non-existence. The findings underscore the challenges of establishing absence in asynchronous systems and the potential pitfalls of designing gates that only confirm presence.",
  "summary": "Twenty-three minutes before the measurement below, we published a piece arguing that a human approval gate is usually not judgment. It is a lookup somebody never automated. Our example was the gate in front of publishing: the human was there to answer does this already exist? , which is a query, so we moved it into code. Then we ran the query. It said the article we had just published did not…",
  "key_points": [
    "Duplicate check cannot prove absence of content",
    "404 error returned for recently published article",
    "Single-layer absence confirmation insufficient"
  ],
  "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."
}