All Collections
Inspectors
Inspectors | Bulk Scheduling Inspectors for Distributed Start Times
Inspectors | Bulk Scheduling Inspectors for Distributed Start Times
Updated over a week ago


In the event that you receive an HTTP 429 error for any inspectors, you may distribute the scheduling for your launchpoints. This guide details the steps for doing so.

HTTP 429 errors mean "Too Many Requests" occurred. An HTTP 429 error is an error from the remote side, i.e. Cisco Umbrella, which means that too many requests are trying to access the API at the same time.

You will see this error with Liongard in the event that multiple Launchpoints are running at the same time. To resolve this, follow these steps.

Select All Child Launchpoints

  • Click the check mark box to select all child launchpoints in the bottom Inspector section

  • Click "Actions" > "Set Inspector Schedule"

    As displayed in the below image:


    Set Times to Space Out Launchpoints

    • In the screen on the right, select the checkbox for "Space These Launchpoints"

    • Set the interval to "5" and units to "minute(s)"

    • Hit Save


      As displayed in the below image:



      The Launchpoints will now be set at the interval specified, and the runs should start at that interval.

      If HTTP 429 errors continue to occur, you may try a larger interval than 5 minutes. Ideally, the interval should be at least the time for the longest-running launchpoint.

Did this answer your question?