[mq] working branch - merge 2c153f4 on top of master at fca18c3

{"baseBranch":"master","baseCommit":"fca18c349a13de2c5c7fee553ca310f5d16eccf8","createdAt":"2025-05-16T16:39:16.034423Z","headSha":"2c153f4c6798de216511f9f30043b69b399bfd01","id":"2dd86707-ed20-4784-854f-a1cb74768d43","priority":"200","pullRequestNumber":"29396","queuedAt":"2025-05-16T16:39:16.033985Z","status":"STATUS_QUEUED"}

Author: dd-mergequeue[bot]

content/en/infrastructure/containers/amazon_elastic_container_explorer.md

@@ -161,7 +161,7 @@ Some resources have specific tags. The following tags are available in addition
 | **Container Instance**         | ~15 minutes               | ~15 minutes                 |
 
 * A newly created ECS Service is typically collected within approximately 15 seconds. However, for status changes in an existing Service, a refresh within 15 seconds is not guaranteed.
-* Installing the Datadog Agent in your cluster enables visibility into task lifecycle changes. Without the Datadog Agent, stopped tasks can appear as running for up to two days.
+* Installing the Datadog Agent in your cluster enables visibility into task lifecycle changes. Without the Datadog Agent, stopped tasks can appear as running for up to 30 minutes.
 * Installing the Datadog Agent in your cluster provides additional, relevant host-level tags, such as `availability_zone`.
 
 [1]: https://app.datadoghq.com/orchestration/explorer/ecsTask