This topic outlines the expiration reminder and shutdown policy for the semi-managed version of Dataphin.
Expiration reminder
Dataphin will send a text message reminder 60, 30, 15, and 1 day prior to the expiration of a semi-managed instance. To prevent service disruption, please ensure you back up your data or renew the instance promptly.
Shutdown policy
Upon expiration, the Dataphin instance will automatically shut down. All tasks will be paused, access to the instance will be blocked, and the creation of scheduled task instances will be unavailable.
Renewal within 360 hours (15 days) post-expiration allows continued use of the Dataphin instance. Note the following release times for dependent cloud products to avoid data loss: please renew within the specified time frame for these products:
ApsaraDB RDS PostgreSQL instance will be released 7 days after expiration, with data becoming unrecoverable. For more information, see RDS PostgreSQL overdue payments.
Cloud Message Queue RocketMQ instance will be released 7 days after expiration, with data becoming unrecoverable. For more information, see Overdue payments.
ApsaraDB Redis instance will be released 22 days after expiration, with data becoming unrecoverable. For more information, see ApsaraDB Redis overdue payments.
Object Storage Service (OSS) instance will be released 15 days after expiration, with data becoming unrecoverable. For more information, see Object Storage Service overdue payments.
Failure to renew within 360 hours (15 days) after expiration will result in the clearing of all tasks and the release of the instance. A text message reminder will be sent 7 days and 1 day before the release.