Recover Policy Safely

Use this directory to select a recovery task. Each linked playbook identifies the required authority and completion evidence. Application programming interface (API) requests require the command’s specific authority. Do not substitute a deployment retry for a corrected policy approval. Do not substitute a Helm rollback for database recovery. Retry continues retained delivery work. Reconciliation compares saved ownership or protection evidence with current observations. Database recovery restores retained local state and still requires checking external effects.

Escalation Data to Collect

Retain the failed action, timestamp, policy identifier, and sanitized response. Include deployment and generation identifiers when available. Refer to diagnostics and escalation to collect evidence within your access. Cluster access is not a prerequisite for reporting a policy failure.

Recover From Failed Release Change

Stop before rolling back workloads against a changed database schema or owner. Helm rollback does not reverse database schema or ownership changes. An older chart might expect credentials that no longer own the database.

Refer to installation and release-change triage. Use the administrator’s qualified deployment or restore procedure. Keep PostgreSQL inside the Policy stack.

Recover From a Partially Failed Policy Deployment

A failed publication might already have changed native resources. Do not delete ownership records or assume that failure means no effect. Refer to publication and withdrawal recovery. That playbook separates retained-artifact retry from corrected-draft reapproval.

Resolve a Missing PIM Ownership Binding

Policy Integration Manager (PIM) bindings connect saved references to native identities. Only a caller with policy:system-configure can inspect and reconcile them. Refer to policy ownership reconciliation. Use only actions that the current inspection permits.

Forget a Verified-Stale PIM Ownership Mapping

Global cleanup removes saved mappings, not native objects. It requires complete inventory evidence and no blocking work. Refer to verified-stale binding cleanup. An unavailable inventory cannot prove native absence.

Recover API Routing

Refer to installation, identity, and routing troubleshooting. Check configured public paths and gateway acceptance before changing chart values. Do not disable authentication or certificate verification as a repair.

Recover a Stalled Publication or Withdrawal

Refer to publication and withdrawal recovery. Retry only eligible current-generation work after resolving its cause. Record manual archive evidence separately from observed deprotection.

For changes that never produced publication work, use automatic recompilation troubleshooting.