From 867a94133da10f751c4e715f566a3457b8c11da5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?=
 <istvan.szabo@elastic.co>
Date: Thu, 10 Oct 2024 18:16:43 +0200
Subject: [PATCH] [DOCS] Removes frozen indices limitation item from anomaly
 detection docs. (#2828)

(cherry picked from commit 04632d2f1d1572bce948963a7ea10c99ab07ff7c)

# Conflicts:
#	docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc
---
 .../stack/ml/anomaly-detection/ml-limitations.asciidoc | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc b/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc
index 2c8eef758..ff4cf3e1f 100644
--- a/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc
+++ b/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc
@@ -94,6 +94,7 @@ Analyzing large arrays results in long strings which may require more system
 resources. Consider using a query in the {dfeed} that filters on the relevant 
 items of the array.
 
+<<<<<<< HEAD
 
 [discrete]
 [[ml-frozen-limitations]]
@@ -105,6 +106,15 @@ items of the array.
 possible to specify the `ignore_throttled` query parameter for search requests
 in {dfeeds} or jobs. See
 {ref}/searching_a_frozen_index.html[Searching a frozen index].
+=======
+[discrete]
+[[ml-frozen-tier-limitations]]
+=== {anomaly-jobs-cap} on frozen tier data cannot be created in {kib}
+
+You cannot create {anomaly-jobs} on 
+{ref}/data-tiers.html#frozen-tier[frozen tier] data through the job wizards in 
+{kib}. If you want to create such jobs, use the APIs instead.
+>>>>>>> 04632d2f ([DOCS] Removes frozen indices limitation item from anomaly detection docs. (#2828))
 
 
 [discrete]