Requeue Dlq Entries
Return exhausted DLQ entries to the retry path (TG-2999).
The inverse of bulk-mark-failed. Use after fixing the underlying cause (a restored proxy URL, a storage permission, an upstream outage) to re-drive the entries that gave up. Without this, the only way to re-drive a DLQ was to lean on natural sync-diff and hope the objects were rediscovered.
Resets max_retries_reached and retry_count, stamps requeued_at, and
clears disposal_reason so the retry task does not immediately re-retire the
entry. Only entries that have EXHAUSTED their retries are touched; anything
still retrying is left alone rather than silently granted extra attempts.
Omit error_types to requeue everything exhausted for the sync config.
Authorizations
Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.
Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.
Body
Request to requeue exhausted DLQ entries back into the retry path (TG-2999).
Optional error-type filter, e.g. ['S3StorageError', 'TimeoutError']. Omit to requeue every exhausted entry for the sync config. Entries that have not exhausted their retries are never touched — they are already retrying.
Response
Successful Response
Response from requeuing DLQ entries.
Number of DLQ entries returned to the retry path.

