diff --git a/tidb-cloud/changefeed-overview.md b/tidb-cloud/changefeed-overview.md
index b81f74f4166dd..23fdb81f481ba 100644
--- a/tidb-cloud/changefeed-overview.md
+++ b/tidb-cloud/changefeed-overview.md
@@ -94,4 +94,4 @@ The states are described as follows:
 - `DELETING`: the replication task is being deleted.
 - `DELETED`: the replication task is deleted.
 - `WARNING`: the replication task returns a warning. The replication cannot continue due to some recoverable errors. The changefeed in this state keeps trying to resume until the state transfers to `RUNNING`. The changefeed in this state blocks [GC operations](https://docs.pingcap.com/tidb/stable/garbage-collection-overview).
-- `FAILED`: the replication task fails. Due to some unrecoverable errors, the replication task cannot resume and cannot be recovered. The changefeed in this state does not block GC operations.
+- `FAILED`: the replication task fails. Due to some errors, the replication task cannot resume and cannot be recovered automatically. If the issues are resolved before the garbage collection (GC) of the incremental data, you can manually resume the failed changefeed. The default Time-To-Live (TTL) duration for incremental data is 24 hours, which means that the GC mechanism does not delete any data within 24 hours after the changefeed is interrupted.