Application Maintenance
Application maintenance tools help authorized support users recover an Application when the Review Tool shows the wrong status.
Repair Review Statuses
Use this action when proposed changes are present but the Review Tool is stuck or shows an incorrect status. For example, an attachment may be waiting for review while the Application still appears as actual.
Open the Application.
In the right side of the toolbar, open Application tools.
Select Repair review statuses.
Read the confirmation and click Repair.
Crewlap checks the complete Review status graph, corrects safe cases, and reloads the Application. The result message distinguishes:
Repaired — all detected issues were corrected.
Partially repaired — safe status repairs were applied, but ambiguous lifecycle issues still need technical investigation.
Needs attention — no safe change was possible and unresolved lifecycle issues remain.
Already correct — no status change or unresolved issue was found.
The message separates ordinary derived-status repairs from terminal descendant repairs. A terminal descendant repair marks an attachment link as deleted when its owning document is already deleted.
The repair does not accept or reject proposed changes. It does not copy suggested values into actual values, edit CV data, delete attachment binaries, or change verification results. An archived document is diagnostic-only: the tool reports an ambiguous descendant state but does not change it.
The action is not available while the Application is being created or deleted, or after it has been deleted or archived. If someone changes the Application while you are repairing it, reload the page and try again.
Permissions
You need all three permissions for the Application:
Applications | Full read
Applications | Update
Applications | Repair review
The built-in ADMINS group receives the repair permission automatically. Other groups must be granted it explicitly. The Application tools menu is hidden when no permitted tool is available.
Every repair attempt that reaches Core successfully creates an Application audit event containing only the Application key, repair categories, issue codes, and counts. It does not include Application personal values.