Identify automation failures and retry conditions
Automation failures occur when required validation, approval, or deployment conditions are not satisfied. Review the automation event details and associated certificate order information to identify the cause of the failure.
Common causes of automation failures
Domain control validation (DCV) requirements not satisfied: The domain validation has expired or the validation artifact is not publicly accessible. Complete domain revalidation before retrying.
Organization validation not complete: OV or EV organization validation has expired or is pending. Complete organization validation before retrying.
DNS validation records not publicly accessible: DNS propagation is incomplete or the TXT record contains an incorrect value.
Automation profile configuration errors: The profile has been disabled due to a policy conflict and has an Action needed status. Resolve the profile settings before retrying. See Create and manage automation profiles.
Deployment environment connectivity issues: The sensor or agent cannot reach the target host or appliance. Confirm network connectivity and sensor configuration.
Insufficient account balance: The account balance is insufficient to process the renewal. Deposit funds before retrying. See Set up account credit.
Retry an automation event
After correcting the issue, retry the automation event using one of the following methods:
In the CertCentral main menu, go to Automation > Automated IPs.
Locate the failed automation event.
Select Retry to rerun the event immediately.
Alternatively, allow the next scheduled automation run to proceed if the issue has been resolved and the schedule is still active.
What's next
Monitor certificate renewal and replacement success to verify that certificate renewal and replacement complete before expiration