At the beginning of February 2025, we will delete inactive environments that are non-recoverable in Cloud Composer 1, Cloud Composer 2, and Cloud Composer 3
Share
Services
## Announcement
At the beginning of February 2025, we will **delete inactive environments that are non-recoverable** in Cloud Composer 1, Cloud Composer 2, and Cloud Composer 3\. After this change, non-recoverable environments that have listed problems will be deleted automatically.
**Cloud Composer 1 and Cloud Composer 2** environments that have both of the following problems present at the same time will be deleted:
* The environment's underlying GKE cluster is deleted.
* The environment is in the ERROR state for at least 60 days because of a disabled billing account or because the Cloud Composer API service was deactivated in its project.
**Cloud Composer 3** environments that have the following problem will be deleted:
* The environment is in the ERROR state for at least 60 days because of a disabled billing account or because the Cloud Composer API service was deactivated in its project.
This change doesn't affect buckets of these environments. You can still recover your DAGs and other data from the environment's bucket and then delete the bucket manually. See [Delete environments](https://cloud.google.com/composer/docs/composer-3/delete-environments#about-not-deleted) for information about data that is not deleted automatically together with the environment.
What else is happening at Google Cloud Platform?
New Dataproc Serverless for Spark runtime versions 1.1.89 1.2.33
about 5 hours ago
Services
Share
The Spanner index advisor is Generally Available in both GoogleSQL and PostgreSQL-dialect databases
about 10 hours ago
Services
Share