An overdue payment or an expired workspace can interrupt running jobs and lead to permanent data loss. Top up your account or renew your workspace within the grace period to restore service and protect your data.
If you do not act within 15 days of a payment becoming overdue or a workspace expiring, all job data is permanently deleted and cannot be recovered.
Usage notes
If your workspace uses Application Real-Time Monitoring Service (ARMS), an overdue payment for ARMS disables the job curve and alerting features.
If your workspace uses storage resources, an overdue payment prevents reading or writing state data and JAR packages, causing jobs to fail over.
Overdue payments
The impact of an overdue payment depends on your billing model. The following table summarizes the effects across all three models.
| Billing model | Days 1–15 after overdue | Day 16 onward | Recovery |
|---|---|---|---|
| Pay-as-you-go | Workspaces suspended; running jobs stopped; compute and management fees stop, but storage continues to be charged | Workspaces released; all job data deleted and unrecoverable | Top up your account |
| Subscription | Jobs continue running; checkpoint and snapshot creation fail; storage continues to be charged | Storage data deleted and unrecoverable | Top up your account |
| Hybrid billing | Elastic resource jobs stopped; fixed resource jobs continue running but checkpoints and snapshots fail; storage continues to be charged | Elastic resources released; workspace reverts to subscription model; storage data deleted and unrecoverable | Top up your account |
Pay-as-you-go
An overdue payment suspends all pay-as-you-go workspaces under your account. If you do not top up within the grace period, the workspaces and all job data are permanently deleted.
Days 1–15 after payment is overdue
All pay-as-you-go workspaces enter an overdue state. Running jobs are stopped.
You cannot access the workspaces.
Compute and management resource fees stop. Storage resources — such as the Object Storage Service (OSS) bucket attached at workspace creation — continue to incur charges.
Top up your account. Once the balance is sufficient, the workspaces resume automatically.
Day 16 onward
The workspaces are considered abandoned and automatically released. All job data is permanently deleted and cannot be recovered.
The data cannot be recovered. Create a new Flink workspace.
Subscription
If payment becomes overdue before your subscription workspace expires, you can still access the workspace. However, you cannot perform fee-incurring operations such as creating new workspaces or renewing orders.
Days 1–15 after payment is overdue
Running jobs continue. All stateful and resource operations — including checkpoint and snapshot creation — fail.
Existing storage resources continue to incur charges.
Top up your account. Once the balance is sufficient, the workspace resumes normally and state writes resume. For renewal details, see Renewal policy.
Day 16 onward
Running jobs continue. Checkpoint and snapshot creation still fail.
The storage service is considered abandoned. All data is permanently deleted and cannot be recovered.
The data cannot be recovered.
After the workspace expires, you cannot use it. For details, see Expiration.
Hybrid billing
If payment becomes overdue before your hybrid billing workspace expires, you can still access the workspace. However, you cannot perform fee-incurring operations such as creating new workspaces or renewing orders.
Days 1–15 after payment is overdue
Jobs using elastic computing resources are stopped. You cannot use or allocate elastic computing resources.
Jobs using fixed resources continue to run. However, fully managed storage and attached OSS may become unavailable, causing checkpoint and snapshot creation to fail.
Existing storage resources continue to incur charges.
Top up your account. Once the balance is sufficient, the workspace and elastic computing resources resume normally, and state writes resume. For renewal details, see Renewal policy.
Day 16 onward
Elastic computing resources are considered abandoned. The workspace reverts to the subscription billing model.
Jobs using fixed resources continue to run. However, because the payment is overdue, fully managed storage and attached OSS may become unavailable, causing checkpoint and snapshot creation to fail.
The storage service is considered abandoned. All data is permanently deleted and cannot be recovered.
The data cannot be recovered.
After the workspace expires, you cannot use it. For details, see Expiration.
Expiration
Subscription and hybrid billing workspaces have a fixed usage period based on the duration selected at purchase. After a workspace expires, you cannot use it. If you do not renew in time, the workspace is automatically released.
| Stage | Resource state | Action |
|---|---|---|
| Before expiration | The system sends reminder notifications by email or text message. | Renew the workspace to continue using it. See Renewal policy. |
| Days 1–15 after expiration | You cannot access the workspace. Online jobs are stopped. | Renew to restore access. |
| Day 16 onward | The workspace is automatically released. Job data is deleted and cannot be recovered. | The data cannot be recovered. |
Resources that you upload, such as JAR packages, are not deleted. They are stored in your OSS.