From 8693147343d18de65a88ef08947e99a7818a4ff2 Mon Sep 17 00:00:00 2001 From: kosabogi Date: Wed, 24 Sep 2025 12:04:14 +0200 Subject: [PATCH] Fixes link --- explore-analyze/transforms/transform-limitations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explore-analyze/transforms/transform-limitations.md b/explore-analyze/transforms/transform-limitations.md index f45503aa69..a94cf6ec2b 100644 --- a/explore-analyze/transforms/transform-limitations.md +++ b/explore-analyze/transforms/transform-limitations.md @@ -128,7 +128,7 @@ If you use ILM to have time-based indices, consider using the [Date index name]( When running a large number of SLO {{transforms}}, two types of limitations can appear: - {{transforms-cap}} may [misreport](#transforms-inaccurate-errors) their state and suggest deletion even though they are still valid -- Point-in-time (PIT) requests may [accumulate](#transforms-pit-storms), creating extra activity on the cluster and slowing down operations +- Point-in-time (PIT) requests may [accumulate](#transforms-pit-overloads), creating extra activity on the cluster and slowing down operations #### {{transforms-cap}} can return inaccurate errors that suggest deletion [transforms-inaccurate-errors]