Integrations
Sync cadence, rate limits, and retries
The behind-the-scenes behavior of integrations: how often they sync, how they stay within source-system rate limits, and what happens when a source is unavailable.
Default sync cadences
Every integration syncs daily by default. You can change the schedule per integration: open Integrations, click Configure on the integration card, and set Sync frequency under Automatic sync.
| Option | When to use it |
|---|---|
| Every 6 hours | High-signal sources such as identity, EDR, and SIEM, where you want changes picked up within the working day. |
| Every 12 hours | Cloud posture and other sources that change often but not constantly. |
| Daily (default) | Most integrations. Plenty for audit evidence and for scanners whose scans run on their own schedule. |
| Weekly | Slow-moving evidence such as training completion. |
| Manual only | No scheduled syncs. The integration only syncs when you click Sync. |
The scheduler checks for due integrations every 6 hours, so a scheduled sync starts on the first check after it comes due rather than at an exact clock time.
Rate limits we respect
Every integration has a known source-side rate limit. Radius360 is written to stay well below those limits even when syncing large tenants, using two mechanisms:
- Static throttles for sources with published rate limits, with headroom budgeted in so steady-state sync traffic does not approach the source's ceiling.
- Retry-After handling for the sources that throttle hardest. When one of them returns 429 Too Many Requests, the sync waits as instructed before trying again (see below).
The net effect: a Radius360 sync should not cause a source-side rate-limit incident on a normally-sized tenant. If you have alerting on API usage, our traffic will be visible but is engineered to stay below normal alert thresholds.
Retry and backoff behavior
When a request is rate limited (429), the Microsoft 365, Okta, GitHub, CrowdStrike, SentinelOne, and Microsoft Sentinel integrations wait for the source's Retry-After header before trying that request again.
A scheduled sync that fails is not retried in the same cycle. The next attempt is the next scheduled sync, or you can click Sync on the integration card once the cause is fixed. If the failure was a credentials problem (401 or 403), fix the credentials first; retrying will not help.
Event-driven updates
Radius360 does not currently subscribe to webhooks or event streams from source systems. Every integration is polled on its schedule, so the fastest path for a new finding is the 6-hour schedule or a manual sync.
Forcing a sync manually
On the integration card in Integrations, click Sync to run an out-of-schedule sync. A notice confirms when the sync completes or shows the error if it fails.
Outbound IP ranges
Radius360 does not publish a list of outbound IP ranges in the app. If your source system only accepts traffic from allowlisted IPs, email support@radius360.co before connecting it and we will work through the options with you.
Related reading: Troubleshooting sync failures, API and webhooks for custom integrations.