Introduction

Renewal Introduction

CodeArts services cannot run after the related subscription expires. To continue using them, renew your subscription within a specified period.

• If a CodeArts package expires without being renewed, code repositories, build tasks, deployment tasks, and other resources will be automatically released. The related data will be lost and cannot be restored. For details about the statuses of a CodeArts package after it expires, see Impact of Expiration.
• If a resource extension or value-added feature expires without being renewed, the related parallel job quotas and features will be unavailable.

Renewal Functions

Table 1 describes the functions related to the renewal of CodeArts.

Take a CodeArts package as an example. You can renew your subscription across the lifecycle of your package, as shown in Figure 1.

Figure 1 CodeArts package lifecycle

• A CodeArts package is in the Normal state from the time when it is purchased to the time when it expires.
• After it expires, the status changes to Expired.
• If the package is not renewed upon expiration, it enters the grace period. If it is not renewed after the grace period ends, the status changes to Frozen.
• If you do not renew your subscription after the grace period ends, your resource enters a retention period. If you do not renew the subscription within the retention period, your resource is automatically deleted.

Auto-renewal can be enabled anytime before a CodeArts subscription expires. The system attempts to automatically renew the subscription at 03:00 seven days before the subscription expires. If the fee deduction fails, there will be one attempt at 03:00 every day until the subscription expires or the renewal is successful. By default, fees are deducted seven days before your subscription expires. You can change this deduction date as required.