Dismiss an extraction failure
POST /admin/metadata-extraction/failures/{id}/dismiss
Removes one failure from the pending queue but keeps its database row.
You need to be signed in with system.admin for the whole install; a permission held only for a team doesn’t count. The path id is the failure row’s ID, not the asset’s. Success returns 204 with no body. Dismissing an already-dismissed row also returns 204 and keeps the first dismissal time. An ID that doesn’t exist when the server checks for it returns 404.
Dismissing doesn’t retry extraction, repair metadata or delete the stored message and raw value. A later extraction failure on the same asset can add a new pending row.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”UUID of the failure row to dismiss, not the asset UUID.
Responses
Section titled “ Responses ”The existing failure is dismissed or was already dismissed. No response body.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedResource not found
object
Human-readable error summary
Example
the request could not be completed