Automation statuses
The automation status indicates the current state of an endpoint with regard to the managed automation solution. You can view the automation status of an endpoint in DigiCert® Trust Lifecycle Manager in the following ways:
Go to the Inventory > Endpoints page, find the location in the table, and check the Automation status column for it. If the Automation status column does not appear, select the Add Column button on the top-right of the table to add it.
Select a location from the Inventory > Endpoints table to view the details for it. The automation status is shown in the top section of the details page.
Table of automation statuses
The following table presents all possible automation statuses in alphabetical order, along with the applicable status types and a description of each status. For an explanation of the type values, see the Legend of status types.
Status | Type | Description |
|---|---|---|
|
| An account was successfully created for the ACME automation service. |
|
| The system failed to create an account for the ACME automation service. |
|
| User intervention is needed to continue automation. |
|
| The certificate issuance request was denied during the approval process. |
|
| The certificate issuance request is awaiting required approval. |
|
| Automation failed due an error with the local DigiCert agent. |
|
| A certificate auto-renewal task has been scheduled. |
|
| The automation process may fail due to a detected issue that requires attention. |
|
| An automation attempt failed due to an unrecoverable error. |
|
| Automation failed due to an issue with the selected certificate profile. |
|
| An automation job has been requested and is in queue to run. |
|
| An automation job has been scheduled and will run at the specified time. |
|
| The previous automation event completed successfully. After 24 hours, this status clears and changes back to |
|
| The certificate was successfully delivered to the target endpoint. |
|
| The system could not deliver the certificate to the target endpoint. |
|
| The certificate was successfully issued. |
|
| Automation is available for this endpoint. An admin can request a certificate automation action on it at any time. |
|
| Automation settings are invalid or incomplete and require correction. |
|
| Automation failed due to an error with an associated connector. |
|
| The system is creating an account for the ACME automation service. |
|
| The system is generating a certificate signing request (CSR) for an automation event. |
|
| The CSR was successfully generated for an automation event. |
|
| The CSR couldn’t be generated for an automation event. |
|
| The system is delivering the issued certificate to the target endpoints. |
|
| Automation failed due to an error with the DNS integration used for domain control validation. |
|
| The ACME challenge succeeded and the domain was validated. |
|
| The certificate was installed but didn’t pass validation checks. |
|
| The system is testing the endpoint to confirm the installation. |
|
| The certificate was installed successfully on the target endpoint. |
|
| The attempt to install the certificate on the target endpoint failed. |
|
| The certificate was installed and has been validated successfully. |
|
| The system is currently installing the certificate on the target endpoint. |
|
| The IP address for the target endpoint is currently unreachable. |
|
| The certificate issuance process failed. |
|
| The certificate authority is issuing the certificate. |
|
| A manual server restart was approved to complete certificate installation. |
|
| Automation is not configured for this endpoint. |
|
| The CSR couldn’t be submitted to the certificate authority. |
|
| The certificate has been issued and is ready for installation. |
|
| The local DigiCert agent encountered an error when trying to run a custom script for the automation. |
|
| The ACME domain validation process failed. |
|
| The ACME challenge process is validating domain ownership. |
Legend of status types
The type values in the preceding table indicate the possible scenarios where each status applies, as follows:
Common: Applies across all automation operations, regardless of endpoint or enrollment method.
Agent: Applies to agent-based automations on web servers.
Sensor: Applies to sensor-based automations for network appliances and cloud services.
Admin web request: Applies to automated certificate delivery via the
Admin web requestenrollment method.Error: Indicates an error status with the associated automation types.