Deferring or Declining an Update

WARNING: This page is about a different car, the 2020 Cadillac CT4. However, it is still accessible from the selected car via links, so may be relevant.

When an OTA update is downloaded, customers have the option to defer or decline the installation. The standard policy for OTA software updates is to set the customer notifications to 30 ignitions cycles. If the customer does not act upon the prompts within this counter, the update package is removed from the vehicle.

If a customer ignores the notification, the ignition cycle counter decreases by one immediately.

If the customer defers the installation by selecting the "Remind Me Later" option, the ignition cycle counter decreases by one, but it will not decrease again until after the customer-selected "Remind Me Later" period, regardless of the number of ignition cycles that occur during that period. For example, if 24 hours is selected for the next remind me time frame and I did 20 ignition cycles, those 20 ignition cycles do not decrease the ignition cycle counter.

NOTE:

For customer use case, standard operating procedure for campaign is to set the notifications to 30 ignitions cycles. If the Customer does not act upon the prompts within this counter, the package / invite is removed from the vehicle. In this scenario, we will wait 2 weeks and re-enroll back into the campaign. FYI: this counter can be selected from 1 to 999 ignition cycles when setting up the campaign.

If the OTA update installation is deferred by the customer, it can be installed at a later date through the Vehicle Softwaremenu under Settings > System on the infotainment screen.

If the customer selects the "Decline Update" option, the update package is immediately removed from the vehicle. In this case, the vehicle will not be re-enrolled to receive the OTA update at a later date, unless the update is a Field Action. OTA updates will not be installed in a vehicle without a customer's consent. There is one exception use case. Constraint Consent use case there is a "May day" counter set in the vehicle, typically 10 ignition cycles. The Customer has that many ignition cycles to complete the update. Upon using all notifications, the installation will take place once this counter has expired. This use case is only for Cyber Critical recall Field Actions and requires Global Safety Field Investigations approval to utilize this use case. To date, this use case has not been used for any field actions.