From 83aca6ac29e3eaa4abc179647c4bbeff2e491181 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Tue, 25 Mar 2025 13:17:04 +0530 Subject: [PATCH 1/3] Update search-job.md --- docs/api/search-job.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/search-job.md b/docs/api/search-job.md index f15429d0d2..ee00ab2eb6 100644 --- a/docs/api/search-job.md +++ b/docs/api/search-job.md @@ -54,7 +54,7 @@ An `HTTP 301 Moved error` suggests that the wrong endpoint was specified. While the search job is running you need to request the job status based on the search job ID. The API keeps the search job alive by either polling for status every 20 to 30 seconds or gathering results. If the search job is not kept alive by API requests, it is canceled. When a search job is canceled for inactivity, you will get a 404 status. -You must enable cookies for subsequent requests to the search job. A 404 status (Page Not Found) on a follow-up request may be due to a cookie not accompanying the request. +You should send ACCESSID:ACCESSKEY pair with every Search Job API request. A 404 status (Page Not Found) on a follow-up request may be due to a cookie not accompanying the request or due to a missing/incorrect ACCESSID:ACCESSKEY pair. There's a query timeout after eight hours, even if the API is polling and making requests. If you are running very few queries, you may be able to go a little longer, but you can expect most of your queries to end after eight hours. From eb2b76361cd398be1e9ecb220691345370d0958e Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 28 Mar 2025 15:45:16 +0530 Subject: [PATCH 2/3] Update docs/api/search-job.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/api/search-job.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/search-job.md b/docs/api/search-job.md index ee00ab2eb6..ce6acf31e8 100644 --- a/docs/api/search-job.md +++ b/docs/api/search-job.md @@ -54,7 +54,7 @@ An `HTTP 301 Moved error` suggests that the wrong endpoint was specified. While the search job is running you need to request the job status based on the search job ID. The API keeps the search job alive by either polling for status every 20 to 30 seconds or gathering results. If the search job is not kept alive by API requests, it is canceled. When a search job is canceled for inactivity, you will get a 404 status. -You should send ACCESSID:ACCESSKEY pair with every Search Job API request. A 404 status (Page Not Found) on a follow-up request may be due to a cookie not accompanying the request or due to a missing/incorrect ACCESSID:ACCESSKEY pair. +You should include the `ACCESSID:ACCESSKEY` pair in every Search Job API request. A 404 status (Page Not Found) on a follow-up request may occur if the request is missing a required cookie or if the `ACCESSID:ACCESSKEY` pair is incorrect or omitted. There's a query timeout after eight hours, even if the API is polling and making requests. If you are running very few queries, you may be able to go a little longer, but you can expect most of your queries to end after eight hours. From e6423bb25a4884bbba30f91743f64430d9688f45 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 28 Mar 2025 15:45:57 +0530 Subject: [PATCH 3/3] Update docs/api/search-job.md --- docs/api/search-job.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/search-job.md b/docs/api/search-job.md index ce6acf31e8..6ef7a33449 100644 --- a/docs/api/search-job.md +++ b/docs/api/search-job.md @@ -54,7 +54,7 @@ An `HTTP 301 Moved error` suggests that the wrong endpoint was specified. While the search job is running you need to request the job status based on the search job ID. The API keeps the search job alive by either polling for status every 20 to 30 seconds or gathering results. If the search job is not kept alive by API requests, it is canceled. When a search job is canceled for inactivity, you will get a 404 status. -You should include the `ACCESSID:ACCESSKEY` pair in every Search Job API request. A 404 status (Page Not Found) on a follow-up request may occur if the request is missing a required cookie or if the `ACCESSID:ACCESSKEY` pair is incorrect or omitted. +You must include the `ACCESSID:ACCESSKEY` pair in every Search Job API request. A 404 status (Page Not Found) on a follow-up request may occur if the request is missing a required cookie or if the `ACCESSID:ACCESSKEY` pair is incorrect or omitted. There's a query timeout after eight hours, even if the API is polling and making requests. If you are running very few queries, you may be able to go a little longer, but you can expect most of your queries to end after eight hours.