All Products
Search
Document Center

Realtime Compute for Apache Flink:Overdue payments and expiration

Last Updated:Jan 14, 2025

Overdue payments or workspace expiration affects the availability of your workspace. To ensure your business continuity, you can top up your account or renew your workplace within a designated timeframe. This topic describes the impact of overdue payments and workspace expiration of Realtime Compute for Apache Flink, as well as the handling policies.

Usage notes

  • If you have an overdue payment for Application Real-Time Monitoring Service (ARMS), the availability of the associated workspace will be affected. To be more specific, the metric visualization and alerting features become unavailable.

  • If you have an overdue payment for the Object Storage Service (OSS) bucket associated with your workspace, resources stored in the bucket, such as state data and JAR files, cannot be accessed. In addition, a failover is triggered for the corresponding job.

Overdue payments

Pay-as-you-go

If your Alibaba Cloud account has overdue payments, your pay-as-you-go workspaces are suspended. If you do not settle the overdue payments within a specific period of time, you can no longer access the workspace. The following table describes the resource availability of a pay-as-you-go workspace within an account which has overdue payments, as well as the recommended actions.

Stage

System policy

Recommended action

Overdue

Within 15 days of the payment due date

  • All pay-as-you-go workspaces that belong to the Alibaba Cloud account are marked as overdue.

  • Access to the workspaces is restricted and all deployments are suspended until overdue payments are settled. While compute or management resources within the workspaces do not generate fees, the OSS buckets linked to these workspaces continue to incur charges.

Top up your account. When your account has sufficient balance, you can continue to use the workspaces.

15 days after the payment due date

The workspace resources are automatically released. The job data of the workspace is deleted and cannot be restored.

The workspace cannot be restored. You need to create a new workspace.

Subscription

If your Alibaba Cloud account has overdue payments before a subscription workspace expires, you can still access the workspace. However, you cannot perform operations that generate fees, such as purchasing a new workspace or renew an order. The following table describes the impact of overdue payments on a subscription workspace and recommended actions.

Stage

Impact

Recommended action

Overdue

Within 15 days of the payment due date

  • The running jobs remain unaffected, but all state and resource operations in the workspace, such as checkpointing and savepoint creation, fail.

  • The existing storage resources continue to incur charges.

Top up your account. When your account has sufficient balance, you can continue to use the workspaces, and the state writes become normal. For more information, see Renewal policy.

15 days after the payment due date

  • The running jobs remain unaffected, but all state and resource operations in the workspace, such as checkpointing and savepoint creation, fail.

  • The storage service is automatically released. All data is deleted and cannot be recovered.

The data cannot be retrieved.

After a workspace expires, the workspace cannot be used. For more information, see Expiration.

Hybrid billing

If your account has an overdue payment before a hybrid-billed workspace expires, you can still access the workspace. However, you cannot perform operations that generate fees, such as purchasing a new workspace or renew an order. The following table describes the impact of overdue payments on a subscription workspace and recommended actions.

Stage

Impact

Recommended action

Overdue

Within 15 days of the payment due date

  • All jobs reliant on elastic resources are stopped, and the elastic resources cannot be used or allocated.

  • Running jobs reliant on fixed resources remain unaffected. But fully managed storage and the linked OSS buckets become unavailable, leading to failures of state and resource operations, such as checkpointing and savepoint creation.

  • The existing storage resources continue to incur charges.

Top up your account. After the account has sufficient balance, you can use the workspace and elastic resources, and the state writes become normal. For more information, see Renewal policy.

15 days after the payment due date

  • Elastic resources are released, and the billing method of the workspace is changed to subscription.

  • Running jobs reliant on fixed resources remain unaffected. But fully managed storage and the linked OSS buckets become unavailable, leading to failures of state and resource operations, such as checkpointing and savepoint creation.

  • The storage service is automatically released. All data is deleted and cannot be recovered.

The data cannot be retrieved.

After a workspace expires, the workspace cannot be used. For more information, see Expiration.

Expiration

Subscription and hybrid-billed workspaces have validity periods based on the subscription durations that you specify when you purchase them. After the duration of a subscription or hybrid-billed workspace ends, you can no longer use the workspace. If you do not renew the workspace within a specific period of time, it will be automatically released. The following flowchart illustrates the changes in resource availability for a subscription or hybrid-billed workspace before and after expiration.

image

Stage

System policy

Recommended action

Before expiration

You are notified by text message and email.

Renew the subscription to continue using the workspace. For more information, see Renewal policy.

After expiration

Within 15 days after expiration

You cannot access the workspace. The running jobs in the workspace are suspended.

15 days after the workspace expires

The workspace resources are automatically released. The job data of the workspace is deleted and cannot be restored.

Note

Resources like JAR packages stored in the linked OSS buckets are not deleted.

The workspace cannot be restored. You must recreate a workspace.

References