From 5e6922f66a7e7821889f254f8ddfbec1d87838b9 Mon Sep 17 00:00:00 2001 From: Alex Dzeda Date: Wed, 3 Apr 2024 09:57:19 -0500 Subject: [PATCH] update runout reference to 429 handling --- _includes/build/requesting_data_runouts.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/_includes/build/requesting_data_runouts.html b/_includes/build/requesting_data_runouts.html index 153fbcf..68bcf20 100644 --- a/_includes/build/requesting_data_runouts.html +++ b/_includes/build/requesting_data_runouts.html @@ -61,9 +61,10 @@

Start a Job using 'runout' with /Group Explanation

If the request was successful, a 202 Accepted response code will be returned and the response will include a Content-Location header. The value of the Content-Location header indicates the location to check for job status and outcome. In the example header above, the number 42 in the URL represents the ID of the export job. The claims returned in the job will be filtered to have a serviceDate of 12/31/2020 or before.

-

- If you're already requesting data from one endpoint and try to request data from that endpoint again while the first request is processing, you'll receive a 429 Too Many Requests error. -

+

+ If you're already requesting data from one endpoint and try to request data from that endpoint again while the first request is processing, you'll receive a 429 Too Many Requests error. For guidance on how to handle 429 errors, refer to our best practices. +

+

Step 3: Check the job status

See Step 3: Check the job status in the Request Data section above.