Checks fail on renders that are genuinely fine — a plate the engine cannot reach, an expectation that does not apply to this shot — and a VALIDATION_FAILED export was a dead end, blocking delivery on a shot a human can see is correct. Override validation on the Export detail page resumes the pipeline where a pass would have handed off: preview, then READY_FOR_QC. It never skips QC and never delivers directly, so the frames are still looked at — the override waives the automated check, not the human one. The failed ValidationResult rows are left untouched rather than rewritten, so the QC queue keeps listing them as warnings and whoever QCs the shot sees what was waved through. The reason is required and recorded with the checks it covered on the export's timeline, and the validation panel keeps an "overridden" badge long after the event scrolls away. Restricted to admin/producer/supervisor: waving a failed check through is a supervisor's call. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -27,6 +27,12 @@ An Export reaches `READY_FOR_DELIVERY` only by passing QC — from the AE panel
|
||||
or the web. That is the single gate; there is no way to package an export that
|
||||
has not been QC'd.
|
||||
|
||||
A render that failed automated validation can still get there: **Override
|
||||
validation** on the Export detail page (admin/producer/supervisor, reason
|
||||
required) resumes the pipeline at the preview stage, so the shot still goes
|
||||
through QC like any other. The failed checks stay on record and keep appearing
|
||||
as warnings in the QC queue, so whoever QCs it knows what was waved through.
|
||||
|
||||
Two rules worth knowing:
|
||||
|
||||
- **Newest version per shot only.** If a shot has two exports sitting ready, the
|
||||
|
||||
Reference in New Issue
Block a user