Editing and Deleting AWP Inspections
Published: 2026-07-21 Revised: 2026-07-21
Because path inspections are tied to the milestones that created them, deleting AWP inspections follows cascade rules. Understanding them prevents accidentally wiping out a whole session — or leaving orphaned path inspections behind.
Deletion cascade rules
| You delete… | Chateau removes… |
|---|---|
| A Starting Milestone | That milestone and all path inspections created in its session |
| An Ending Milestone | That milestone and all path inspections created in its session |
| A single Path Inspection | Only that one path inspection; the milestones and other paths remain |
Deleting either milestone of a session removes that session's path inspections, because without both a start and an end point the session boundaries no longer exist.
The other milestone is not affected. Deleting a milestone removes that milestone and its session's path inspections only — the opposite milestone of the session stays in place.
Deleting a single path inspection is exactly what you do in Method 2 of Handling Leaks During an AWP Survey — you remove the incorrect auto-pass on a leaking component so you can record a failing OGI inspection instead.
Fixing an ending milestone on the wrong component
This is fully supported. If you record an ending milestone and then realize it should have been a different component:
- Delete the incorrect Ending Milestone. This removes it and the session's path inspections, but leaves the Starting Milestone in place — the session is open again.
- Record a new Ending Milestone on the correct component. Chateau recreates the path inspections between the starting milestone and the new ending milestone.
(Deleting a starting milestone behaves the same way — only that milestone and the session's path inspections are removed; the ending milestone remains.)
The "Bad Milestone" prompt
If a technician tries to record a milestone on a component that already has a path inspection from a previous session, Chateau warns that the route may be out of sequence:
- Bad Milestone — "This component already has a Path inspection recorded. Would you like to continue with the inspection anyway?"
- Yes — the milestone is recorded on the component.
- No — Chateau asks the next question.
- Report Bad Route? — "Would you like to report a bad route for this component?"
- Yes — starts the Bad Route field event workflow so the route can be reviewed. No inspection is recorded.
- No — nothing is recorded, and you return to the component details.