Skip to main content
doubleohseven
Explorer
Apr 4, 2024 4:00 PM UTC
Solved

Handling Crowdstrike API Rate-limiting errors

Hi all,


Wondering if anyone has any suggestions for dealing with 429 Rate Limit exceeded messages when using the Crowdstrike connector. I run multiple enrichment automations using different Crowdstrike actions and they often trigger the rate limiting error below:
{
"Error message": "HTTP Status Code 429: Too Many Requests Details:API rate limit exceeded. Connector :: crowd-strike-falconV2.3.1",
"failed_step_id": 530078,
"failed_workflow_id": 68102,
"status": "failed",
"execution_time": "42 seconds 480 ms"
}

I'm wondering how to approach this, perhaps using a "do until" loop to check to make sure status is not failed?

Any help would be greatly appreciated, thanks!

    doubleohseven
    Explorer
    Apr 11, 2024 5:28 PM UTC

    Hi all, I was able to do this by adding a do until loop on the connector action that had the condition of vars.step_result.status == 'Success'

    1 reply

    doubleohseven
    doubleohsevenAuthorAnswer
    Explorer
    Apr 11, 2024 5:28 PM UTC

    Hi all, I was able to do this by adding a do until loop on the connector action that had the condition of vars.step_result.status == 'Success'

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT