List recent extraction backfills
GET /admin/metadata-extraction/backfills
Returns the most recently created metadata-extraction backfill runs.
You need to be signed in with system.admin for the whole install; a permission held only for a team doesn’t count. system.metadata_extraction.read, which opens the failure queue, doesn’t open this list. Runs started by any administrator are included, completed and cancelled ones too.
Results are newest first by started_at, and ties have no fixed order. limit defaults to 20, up to 50. There’s no offset, cursor or total count, so you can’t page back to older runs. With no runs you get items: [].
The counters track attempts to queue extraction jobs, not whether those jobs finished or extracted any metadata. Reads go straight to the database, and a running sweep saves its progress between batches on a best-effort basis.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Maximum number of recent runs to return, from 1 to 50. Defaults to 20.
Responses
Section titled “ Responses ”Recent run records, newest first. An empty list is returned as items: [].
A bounded list of recent backfill runs, with no pagination token or total count.
object
Run records, newest first by started_at; ties have no fixed order. Empty when no runs exist.
A recorded backfill sweep. Its counters track attempts to queue child extraction jobs, not whether those jobs finished or extracted values.
object
UUID of this backfill run. It is not the coordinator job ID.
The singleton asset-type filter, if one was sent; left out otherwise. It doesn’t reflect asset_type_refs, extension filters or the non-image flag, so its absence doesn’t mean the run was unfiltered.
Always zero in the current implementation, even after completion. It isn’t a count of eligible assets.
Queueing attempts counted by whichever coordinator attempt last saved progress. A retry restarts the count, and an asset can be counted more than once.
Queueing attempts that returned no error. It doesn’t count successful metadata extractions.
Queueing attempts that returned an error. Failures inside the child extraction jobs aren’t counted here.
When the run row was inserted, before the coordinator was queued. It doesn’t show when a worker started processing.
When the coordinator finished its sweep; left out until then. Child extraction jobs can still be queued or running.
When the first accepted cancellation request for an unfinished run was recorded; left out until then. It doesn’t confirm that the worker has stopped.
Account reference of whoever started the run. Left out when unavailable, including after that account is hard-deleted.
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 completed