Reviewers decide which reviewed release production uses and can retire reference data. RefillFlow also allows reviewers to draft rules and examples, so examine your contribution status before activation. Reviewer authority does not include operational floor or stores work.
Review the saved candidate
Open Rules and releases, inspect the active release and current saved draft, then Prove the saved draft. Under Review the release candidate, read the rules in order, default outcome, escalation policies, examples, every input of every loop and the changes against the active release.
Check the whole business result: queue, priority, due target, urgency approval and escalation timing. Passing a single condition is insufficient. Confirm that the receiving locations, loop quantities and allowed queues are the intended current configuration. The release's default queue must already be enabled. Ask the owner to enable it on Stores queues before proof and release; if enablement changes the configuration after proof, rebuild and review the candidate.
Apply the exact independence rules
Only a reviewer can choose Release rules, with recent Accounts verification. If you changed the release and the site requires a distinct reviewer, another person must activate it. If the site permits self-review, the screen requires a recorded statement describing what you checked. Merely holding author and reviewer roles does not create independence.
Automation-managed candidates have additional separately retained expectation and release reviews. Their independence checks still apply even if local self-review is allowed. Resolve those reviews in the linked Automation workflow rather than treating native activation as a bypass.
Deal with a stale or faulty candidate
A change to the draft, configuration or active assignment can stale the candidate. Rebuild proof and review current evidence. Do not activate an earlier hash because its report looked right before the change.
Rollback selects a release that was active before and checks it against current dependencies and plan, with a reason and recent verification. An Automation-managed workflow can refuse a direct rollback and require a reviewed candidate instead. Existing admitted cycles retain their original obligations.
Reference retirement is a separate immediate decision. Inspect open work and the stated effect before retiring an item, queue, location, loop or container. See rules and releases.
For item, location, queue, loop or container retirement, follow reference data. Resolve dependency order and open obligations explicitly; retiring a reference is separate from cancelling a refill.