Enrichment Status

Retry permanently-failed enrichments for a tenant

Changed on

Clears the terminal failure markers for a tenant so the reconciler will attempt those records again.

The automatic sweep deliberately never revives a terminal record: a terminal failure is a property of the record's own text — a content-policy block, a refusal, an input past the model's limit — so re-running it costs a provider call and fails identically. This endpoint is the override for when that premise has changed: the text was edited, or the provider changed its policy.

Because of that, it is rate limited per (tenant, enrichment). Clearing is a request to spend a provider call on every record already known to fail, so an unbounded clear would be a cost-amplification loop. A refused call returns cooling_down with the remaining wait rather than silently doing nothing.

Every requested enrichment gets its own outcome — a tenant can have one cleared, one cooling down and one switched off in the same call. Responds 202: clearing is synchronous, but the retrying is not.

post/v1/tenants/{tenant_id}/enrichments/retry

Request

  • Base URL
    http://localhost:8080
  • URL
    http://localhost:8080/v1/tenants/{tenant_id}/enrichments/retry
  • Auth
    HTTP bearer

Path parameters

tenant_idstring required

The tenant whose terminal failures should be cleared.

Request body

enrichmentsstring[]

Which enrichments to clear. Omit or leave empty for all of them, which is the usual call. An unknown name is rejected rather than ignored, so a typo cannot come back as a successful no-op. A list longer than the three names is rejected too.

Response

Accepted; see each enrichment's outcome.

tenant_idstring required

Changes