Infraova
Resources›Guides›How to handle failed remediation

Guide

How to handle failed remediation

Diagnose a remediation that did not produce the expected result and determine the appropriate next step.

AgencyEnterprise·5 min read

The situation

Occasionally a remediation executes but verification does not pass — the live DNS state does not match the expected value. This can happen due to propagation delays, provider API issues, or a problem with the proposed value itself.

Before you begin

A failed verification result in Infraova
Access to the DNS provider to check the current record state
Understanding of what the expected state should be

The operational path

01Identify failure
02Check provider state
03Diagnose cause
04Decide next step
05Re-verify

The goal isn't just to find the error. The goal is to move from detection to a verified infrastructure state.

What could have caused this?

Cause

What changed

Possible impact

Propagation delay

Change applied but not yet propagated

Verification ran too early — wait and re-check

Provider API error

Change was not applied by provider

Record unchanged — retry required

Conflicting record

Another record interferes with the change

Applied value overridden or ignored

Wrong proposed value

The proposal itself contained an error

Fix applied incorrectly — requires revised proposal

Step by step

01Check the provider directly

Before diagnosing further, check whether the change was actually applied.

What to check

✓Log in to the DNS provider account
✓Find the record that was supposed to change
✓Confirm whether the new value is present or the old value remains
02Diagnose the failure cause

Use what you found at the provider to determine why verification failed.

What to check

✓If the record shows the new value: propagation delay — wait and re-verify
✓If the record shows the old value: the change was not applied — check for API errors
✓If the record shows a different value: conflicting change or incorrect proposal
03Take corrective action

Based on the diagnosis, decide the appropriate next step.

What to check

✓For propagation delays: wait for TTL expiry and re-run verification
✓For API errors: retry the approved remediation through Infraova
✓For incorrect proposals: decline and create a revised one
✓For conflicting records: resolve the conflict first, then re-apply

With Infraova

If verification fails, Infraova keeps the issue open and records the failure. Nothing closes as "done" when it isn't.

04Re-verify after corrective action

After taking corrective action, confirm the expected state is now live.

What to check

✓Re-run verification in Infraova
✓Confirm the live value matches the expected value
✓Confirm the original issue is now resolved

Expected result: Verification passes. The issue is resolved and the remediation record is complete.

You decide. Infraova executes.

Infraova can propose and execute an approved infrastructure change, but it does not independently decide to modify client infrastructure. Every proposed change requires explicit authorization before execution.

Infraova detects
↓Infraova diagnoses
↓Infraova proposes
↓YOU APPROVE
↓Infraova executes
↓Infraova verifies

Key takeaway

A failed verification is information, not a failure of the process. Diagnose the cause, take the right corrective action, and verify again.

Turn this playbook into a continuous workflow

Without Infraova

Someone discovers the issue
↓Someone investigates manually
↓Someone decides what to do
↓Someone makes the change
↓Someone checks whether it worked

With Infraova

Monitor
↓Detect
↓Prioritize
↓Propose
↓Approve
↓Remediate
↓Verify
↓Record

The guide teaches you how to solve the problem once. Infraova keeps watching for it after you're done.

Start monitoring →Learn how Infraova works →

Continue the playbook

How to verify a DNS change

Read guide →

How to review a proposed DNS change

Read guide →

Want the product-level details?

Guides answer "How do I solve this?" Documentation answers "How does Infraova work?"

Remediation →Verification →

Stop discovering infrastructure problems manually.

Infraova continuously monitors your client and business infrastructure, identifies meaningful problems, proposes the next action, executes approved changes, and verifies the result.

Start monitoring →Explore Infraova →