GitOpsHQ Docs
Quickstart

Common Mistakes And Fast Fixes

The most common usage mistakes and how to recover quickly.

Use This Page During Real Work

When actions are blocked or outcomes are confusing, match the symptom first, then apply the shortest safe recovery path.

Common Mistake Patterns

  • User expects action visibility based on team name only.
  • Action is hidden/disabled because effective permission is missing.
  • Fix by validating role + resource grant, then re-open action screen.
  • User expects immediate execution after request creation.
  • Request remains pending because quorum is not satisfied.
  • Fix by checking eligible approvers and gate progress detail.
  • Deploy/promotion fails unexpectedly in production.
  • Environment is frozen or has stricter policy than expected.
  • Fix by confirming freeze reason and intended unfreeze path.
  • Rollback is requested without validating target impact.
  • Recovery creates broader change than intended.
  • Fix by running preview and narrowing to service/field scope.

Fast Recovery Sequence

Identify blocker type: permission, approval, policy/freeze, or runtime.
Open matching module and verify current state badges.
Apply smallest corrective action.
Re-run preview before execution retry.
Confirm audit evidence for the corrective action.

Where To Jump Next

  1. Policy and Approvals
  2. Release Lifecycle
  3. Rollback Operations
  4. Go-Live Readiness
  5. Runbooks

On this page