Operations
Remediation
What happens after approval — how Infraova executes the approved change against the connected provider and tracks the result.
What remediation is
Remediation is the execution stage — the point where an approved proposal becomes an actual change in the connected infrastructure. Infraova takes the approved change, calls the provider API, and applies the modification. For DNS changes, this means writing, updating, or deleting the specific record in the connected DNS zone. The change happens through the same provider connection that Infraova uses for monitoring.
The execution flow
Once a proposal is approved, Infraova queues it for execution immediately. The execution flow begins by authenticating with the provider, locating the correct zone and record, applying the change, and recording the result. The entire flow is logged — every API call, every response, every status transition — so the complete execution history is available in the audit trail.
Execution status
Infraova tracks execution status in real time. Queued means the change is waiting to be executed. Executing means Infraova is actively communicating with the provider API. Completed means the provider confirmed the change was applied. Failed means the execution encountered an error. You can see the current status from the proposal detail view.
DNS remediation specifics
For DNS changes, Infraova writes records through the provider's DNS management API. The change is applied to the zone on the provider's nameservers. DNS propagation — the time it takes for the change to be visible across the global DNS system — happens after the record is written. Infraova accounts for propagation time in the verification stage and does not mark an issue resolved until propagation is confirmed.
Failed remediation
If execution fails, Infraova records the failure and the reason — an API error, an authentication failure, a rate limit hit, a conflict with an existing record. A failed remediation does not close the issue. The proposal returns to a Failed status with the error detail visible. You can retry the execution from the proposal view once the underlying cause is resolved.
Note
A failed remediation means the change was not applied. The infrastructure remains in its previous state. Infraova will surface the issue again on the next monitoring pass.
What Infraova does not remediate
Infraova only executes changes through connected providers with write access granted. It cannot modify infrastructure on providers that are not connected, and it cannot make changes to systems outside its connected integrations. Issues on unconnected infrastructure are surfaced for manual resolution.