From 2a3e6ccc6d145737c01c83c97e0995291ccfe6cc Mon Sep 17 00:00:00 2001
From: Jagadisha V <129049263+JV0812@users.noreply.github.com>
Date: Fri, 20 Feb 2026 12:55:09 +0530
Subject: [PATCH] Update search job rate limit documentation

Removed specific rate limits for Frequent Tier and Flex data searches.
---
 docs/api/search-job.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/api/search-job.md b/docs/api/search-job.md
index 269175cdcd..f50eeb73ff 100644
--- a/docs/api/search-job.md
+++ b/docs/api/search-job.md
@@ -87,10 +87,6 @@ import RateLimit from '../reuse/api-rate-limit.md';
 
 A limit of 200 active concurrent search jobs applies to your organization.
 
-When searching the [Frequent Tier](/docs/manage/partitions/data-tiers), a rate limit of 20 concurrent search jobs applies to your organization.
-
-When searching the [Flex data](/docs/manage/partitions/flex), a rate limit of 200 concurrent search jobs applies to your organization.
-
 Once you reach the limit of 200 active searches, attempting an additional search will return a status code of `429 Too Many Requests`, indicating that you've exceeded the permitted search job limit.
 
 This limit applies only to Search Job API searches, and does not take into account searches run from the Sumo UI, scheduled searches, or dashboard panel searches that are running at the same time. If the search job is not kept alive by API requests every 20-30 seconds, it is canceled.