Overview 💥
Running Inspector launchpoints all at once can create high demand on both target systems and Liongard infrastructure. With bulk scheduling, you can stagger launchpoint execution to avoid overloading APIs and improve inspection reliability.
This is especially useful when you have many inspectors, multiple tenants, or heavy inspection workloads.
Distributed scheduling ensures:
API calls are made more evenly
Inspectors don’t all fire at once
More predictable inspection patterns
Reduced risk of rate limiting or throttling
Why Use Distributed Start Times? 🤔
Here are the key benefits of spreading out your inspector launchpoints:
Benefit | Description |
Avoid API Rate Limits | Distributing run times reduces bursts of API requests, helping you stay under rate limits on vendor platforms (e.g., Microsoft, AWS, Google). |
Improved Inspection Success Rate | Fewer simultaneous runs mean fewer failures due to contention or resource saturation on target systems. |
Balanced Load | Rather than launching dozens or hundreds of inspectors at once, a well-spaced schedule minimizes spike risk. |
Flexibility & Control | You decide whether you want all inspectors to run at once or gradually over time, based on your maintenance windows and monitoring goals. |
How to Bulk-Schedule Inspector Launchpoints 🧑🏫
Use this step-by-step process to configure distributed start times in the Liongard portal:
Open Liongard Portal
Go to Admin → Inspectors → Select Inspector Type.Select Inspectors
Select all the inspectors you want to reschedule at once (in bulk).
Open the Scheduling Menu
Click the Actions tab, then choose Set Inspector Schedule.
Configure Scheduling Options
In the schedule panel on the right, you have two choices:Set Next Schedule Run Date / Time — Assign a single, synchronized future run for all selected launchpoints at once.
Space These Launchpoints Out By — Distribute the launchpoints over a period using your choice of interval (minutes / seconds / hours).
Enter Your Settings and Save
If setting a specific date/time: pick the date and time for the next run.
If spacing launchpoints: choose how far apart (e.g., 5 minutes, 30 seconds, 1 hour).
Click Save to apply.
Example Scenarios 🤩
Here are two real-world scheduling scenarios to illustrate how you might use these options:
Scenario | Scheduling Approach |
Nightly Maintenance | Use Set Next Run Date / Time to run all inspectors at 2:00 AM once. |
Large Number of Inspectors | Use Space These Launchpoints with a 5-minute interval so that 20 launchpoints run between 2:00 AM and 2:55 AM instead of all at once. |
Best Practices 🚀
Start conservative: For many launchpoints, begin with a 3–5 minute spacing, then monitor results.
Know your inspector runtimes: Understand how long your different inspectors typically run to pick an effective interval.
Adjust for growth: Whenever you add new launchpoints, revisit your schedule to ensure spacing still makes sense.
Use off-peak times: If available, schedule your bulk runs during lower-activity windows to reduce impact.
Document your schedule logic: Keep a record of how you've staggered inspectors to help with future troubleshooting or auditing.
When to Contact Liongard Support 🦁
Please contact Liongard Support if:
You continue to see HTTP 429 errors after enabling distributed scheduling.
Inspectors are still failing or timing out despite a spaced schedule.
You're unsure what interval works best for your environment.
You want to validate or optimize your bulk scheduling configuration.
Useful information to include:
The list of launchpoints you scheduled
The interval or time you selected
Any inspector error logs (if failures occur)
Relevant API error messages or rate-limiting notes
Our Support team is always happy to help 😇
💬 Start a chat with Leo (Our AI Assistant) or connect with a live support engineer.
📧 Email: support@liongard.com