Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

CloudFront error when calling Management Unit Schedules API

  • 1.  CloudFront error when calling Management Unit Schedules API

    Posted 06-05-2025 18:06

    mguanlao | 2021-10-19 03:12:31 UTC | #1

    Hi,

    We are using the API call - /api/v2/workforcemanagement/managementunits/{managementUnitId}/schedules/search

    It used to return records without any problems, but recently we have been receiving 429 errors and seeing "Error from cloudfront" in the Response Header.

    I understand that 429 are rate limit errors but I do not understand why we are receiving cloudfront error along with it.

    Here is the cloudfront error in the ResponseHeader: {"Name":"X-Cache","Value":"Error from cloudfront","Type":3,"DataFormat":2,"ContentType":null}

    Any help would be much appreciated.

    tim.smith | 2021-10-19 16:45:49 UTC | #2

    You can find more information about rate limits, including best practices for handling being rate limited, here: https://developer.genesys.cloud/api/rest/rate_limits. If you can provide a correlation ID for the response, I can see if there's any additional information available.

    brian.trezise | 2021-10-19 17:15:50 UTC | #3

    Unrelated to the 429s, I wanted to chime in and point out that the route you're using (POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/schedules/search is actually deprecated.

    The preferred route to use would be one of

    1. POST /api/v2/workforcemanagement/businessunits/{businessUnitId}/agentschedules/search

    for searching across management units within a business unit or

    1. POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/agentschedules/search

    to continue to search solely within a single management unit

    It doesn't look like this would have anything to do with the 429s you're seeing, but the new routes are better optimized for performance.

    As Tim Smith mentioned above, to do further investigation into the 429s you're receiving we would need a correlationId

    mguanlao | 2021-10-19 23:32:40 UTC | #4

    Hi Tim,

    Thanks for your response.

    We have a retry function set in place which is dependent on Retry-After as mentioned in the link you gave. However, this particular error does not contain a Retry-After in the header.

    I am more curious as to why we are receiving an "error in cloudfront" in the response header. It would be much appreciated if you could shed more light to that.

    Here is the correlation ID by the way, 8bd35fca-95d5-4d8c-9055-d3f302c699be

    Thanks and regards.

    mguanlao | 2021-10-19 23:34:42 UTC | #5

    Thanks for this. Updating the deprecated API's is in our roadmap.

    tim.smith | 2021-10-20 13:20:59 UTC | #6

    mguanlao, post:4, topic:12399
    Here is the correlation ID by the way, 8bd35fca-95d5-4d8c-9055-d3f302c699be

    I'm not seeing any traces for that correlation ID. If you require further investigation into that response, please open a case with Genesys Cloud Care to continue investigating.

    mguanlao | 2021-10-20 22:16:14 UTC | #7

    Hi Tim,

    Thanks again for looking into this.

    Any idea on the cloudfront error?

    tim.smith | 2021-10-20 22:27:59 UTC | #8

    Please open a case with Genesys Cloud Care to continue investigating as this is a product issue and not a typical usage issue and cannot be investigated via the forum.

    mguanlao | 2021-10-20 22:32:41 UTC | #9

    tim.smith, post:8, topic:12399
    Genesys Cloud Care

    Ok thanks. Appreciate the help.

    system | 2021-11-20 22:33:34 UTC | #10

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 12399



Related Content