# Start Custom Ingredient Pin Drift Scan

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

Start a background scan that lists the organization's recipes still using an older version of this custom ingredient. The scan compares each recipe with the version that is current when it starts, and changes no recipe, ingredient or label.

Returns the job at once (`queued`). Read it with `getJob` until its state is `succeeded`, `partially_succeeded` or `failed`. A `succeeded` item is one recipe on an older version: `subject_ref` holds the recipe id, name and status, `pinned_version_id`, `current_version_id`, and `label_affecting` with the changed `label_affecting_fields`. `label_affecting_fields_known: false` means the older version could not be read, so a person should check the recipe. A `skipped` item gives its reason in `detail`, for example `pinned_newer_than_scan` for a recipe moved to a version made after the scan started. A recipe on the current version gives no item. `result` counts the recipes scanned and behind. Any ingredient status can be scanned; the job fails with `subject_not_found` if the ingredient is deleted while it runs.

The recipe list comes from a near-real-time index, so a recipe saved seconds before the scan may not be counted yet. An organization runs at most 5 jobs at a time.
