tencent cloud

Elastic MapReduce

  • Release Notes and Announcements
  • Product Introduction
  • Purchase Guide
    • EMR on CVM Billing Instructions
    • EMR on TKE Billing Instructions
    • EMR Serverless HBase Billing Instructions
    • EMR Serverless TCBase Billing Overview
  • Getting Started
  • EMR on CVM Operation Guide
    • Planning Cluster
    • Administrative rights
    • Configuring Cluster
    • Managing Cluster
    • Managing Service
    • Monitoring and Alarms
    • TCInsight
  • EMR on TKE Operation Guide
  • EMR Serverless HBase Operation Guide
  • EMR Serverless TCBase Operation Guide
  • EMR Development Guide
    • Hadoop Development Guide
    • Spark Development Guide
    • Hbase Development Guide
    • Phoenix on Hbase Development Guide
    • Hive Development Guide
    • Presto Development Guide
    • Sqoop Development Guide
    • Hue Development Guide
    • Oozie Development Guide
    • Flume Development Guide
    • Kerberos Development Guide
    • Knox Development Guide
    • Alluxio Development Guide
    • Kylin Development Guide
    • Livy Development Guide
    • Kyuubi Development Guide
    • Zeppelin Development Guide
    • Hudi Development Guide
    • Superset Development Guide
    • Impala Development Guide
    • Druid Development Guide
    • TensorFlow Development Guide
    • Kudu Development Guide
    • Ranger Development Guide
    • Kafka Development Guide
    • StarRocks Development Guide
    • Flink Development Guide
    • JupyterLab Development Guide
    • MLflow Development Guide
  • Practical Tutorial
    • Practice of EMR on CVM Ops
    • Data Migration
    • Practical Tutorial on Custom Scaling
  • API Documentation
    • History
    • Introduction
    • API Category
    • Making API Requests
    • Cluster Resource Management APIs
    • Cluster Services APIs
    • User Management APIs
    • Information Query APIs
    • Scaling APIs
    • Configuration APIs
    • Other APIs
    • Cluster Lifecycle APIs
    • Serverless HBase APIs
    • YARN Resource Scheduling APIs
    • Data Types
    • Error Codes
  • FAQs
    • EMR on CVM
  • Service Level Agreement
  • Contact Us

Overdue Payments

Download
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-04-30 15:41:47

Yearly/Monthly Subscription Instances

After you specify the message recipients and notification methods
on the
Message Subscription Management page, you will receive the following alarm information.

Alarm Description

Alarm Type
Description
Expiration Alarm
The system pushes expiration alarm messages of cloud resources to users on the 7th day, 5th day, 3rd day, and 1st day before expiration, as well as on the day of expiration. The alarm messages will be sent through email or short message service (SMS) to the creator of the Tencent Cloud account, global resource collaborators, and financial collaborators.
Payment Overdue Alarm
On and after the day of cloud resource expiration, payment overdue isolation alarm messages will be pushed to users. The alarm messages will be sent through email or SMS to the creator of the Tencent Cloud account and all collaborators.

Recycling Mechanism

The system will send you renewal reminder notifications within 7 days before the cloud service resource expires.
If your account balance is sufficient and automatic renewal is enabled, the resources will be automatically renewed on the day of expiration.
If your instance is not renewed before expiration (or on the day of expiration), the system will suspend the service within approximately 48 hours after expiration (the device will be isolated but not powered off, and data will be retained). The instance will be moved to the recycle bin.
Instances not renewed upon expiration will not incur fees, but network fees will still be charged.
You can renew and restore instances within 7 days from the start of service suspension.
Note:
The start time of the renewal cycle for instances restored via renewal is the expiration date of the previous cycle.
If your instance is not renewed within 7 days after service suspension (including the 7th day), the system will release the resources within approximately 24 hours after the 7-day suspension period. Data in the expired instance will be cleared and irrecoverable.

Pay-As-You-Go Instances

Payment Overdue Notification

Alarm Type
Description
Payment Overdue Notification
The system deducts fees for pay-as-you-go resources on the hour, every hour. When your account balance becomes negative, we will notify the creator of the Tencent Cloud account, global resource collaborators, and financial collaborators via email and SMS.

Payment Overdue Handling

When your account balance becomes negative, pay-as-you-go instances can continue to be used and billed for 2 hours. After 2 hours, billing will stop, and the instances will be automatically suspended and moved to the recycle bin.
Time After Auto-Suspension
Description
≤ 15 days
1. If the balance becomes positive after top-up, billing will resume and the instances will be automatically restored.
2. If your account balance has not been topped up to a positive balance, the instances cannot be restored.
> 15 days
If your account balance is not topped up to a positive amount, pay-as-you-go instance resources will be reclaimed and released. All data will be cleared and become irretrievable. When instance resources are reclaimed, we will notify the creator of the Tencent Cloud account and all collaborators via email and SMS.
Note:
Please terminate pay-as-you-go instances in a timely manner when they are no longer in use to avoid further charges.
After instances are terminated, the data will be cleared and become irretrievable.
Due to potential changes in your actual resource consumption, there may be certain errors in balance alarms.
During the payment overdue isolation period, network fees and associated services will continue to be charged normally until the account balance becomes negative.


도움말 및 지원

문제 해결에 도움이 되었나요?

피드백