Continuous Delivery - Paused Due to Failed Attempts

The backend monitoring service performs some validations on the continuous delivery settings, before starting the actual check of the remote file. If the settings are invalid, it stores the failed attempt and exits the process, until the next iteration begins. The validations it performs are the following:

• The URL of the remote file has been provided
• The default publisher provided exists
• The default publisher provided owns a personal access token
• The default publisher provided has permission to manage the virtual appliance in question

If many failed attempts to start the process occur successively, the monitoring service pauses continuous delivery for the virtual appliance in question and displays the latest error in the AppDB portal.

In order to resume continuous delivery, users must resolve these issues first.