A paused rollout moves when someone on your team approves
Where Argo is configured (your organization opts in), FixControl reads rollout status and opens a deployment gate. The rollout stays paused until someone on your team approves the gate; only then is the promotion dispatched.
How a gated promotion works
Rollout status
Where Argo is configured, FixControl reads rollout and deployment status, scoped to your tenant. The gate is opened against the state Argo reports.
Deployment approval gate
A deployment approval gate makes promotion an explicit, attributed decision. Until the gate is decided, the rollout stays paused.
Human-approved promotion
Approving the gate is what promotes the paused rollout. There is no promotion path that skips the gate.
Abort & rollback visibility
Where Argo reports abort and rollback state, FixControl surfaces it during the gate. The approver sees what the rollout is doing before deciding.
Scoped & gated
Promotion runs only through the gate and only under the Argo access you configured. Argo governance is opt-in per tenant; nothing is gated or promoted unless you set it up.
Evidence & audit
The promotion decision is recorded with the approver, their role, and the evidence they saw. Rollout history and the decision ledger match.
Status read and promotion are separate capabilities
Argo may be reachable for status while promotion isn’t configured, or the reverse. FixControl tracks the health of each path on its own, so the gate reflects what is wired up.
Available where Argo is configured and reachable. Status reads keep the deployment gate tied to the rollout’s live state.
FixControl opens the gate as a recorded, attributed step. The promotion decision that follows is always a person’s.
Runs where Argo is configured, and only after the gate is approved. The promote call is dispatched through the integration outbox.
Shown where Argo is configured to report it, so abort and rollback state is visible while the gate is pending.
Doesn’t exist here. A paused rollout is promoted by an approved gate decision or not at all.
Not used. Status read and promotion report health separately, so a broken promote path can’t hide behind a working status read.
The gate holds until someone decides
Deployment gate questions
Does FixControl deploy to production on its own?+
What does FixControl need to promote a rollout?+
What happens if a promotion fails?+
Can FixControl roll back automatically?+
Are deployment promotions audited?+
Gate your next promotion
Book a demo and approve a paused rollout yourself — where Argo is configured, promotion waits for exactly that.