---
title: "Cron Rescan Errors"
method: POST
path: "/v2/safety/cron/rescan-errors"
tags: ["v2 - Content safety"]
---

# Cron Rescan Errors

`POST /v2/safety/cron/rescan-errors`

## Request

- Base URL: `https://api.jubjubapp.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.jubjubapp.com/v2/safety/cron/rescan-errors`
- Auth: HTTP bearer

Pieces held on a scan error, scanned again: a few per run, newest
first, inside a wall-clock budget that fits the job's attempt deadline
(320 s, cloudbuild.yaml schedule-safety-rescan-errors). A piece that
clears is released the way an admin clear releases it; one still
failing after five attempts stays held as scan_error:gave_up.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/jubjubapp/apis/jubjub-api.md) - [All operations](https://skmtc.dev/jubjubapp/apis/jubjub-api/llms.txt) - [OpenAPI document](https://skmtc.dev/jubjubapp/apis/jubjub-api/revisions/353157b296f2?raw)
