Thanks, that detail helps. Counts landing on exact thousands make me think this isn't a 429 at all. It looks more like the pull stops paginating early, either because it hits a page or result cap or because a run times out partway through, so you get N full pages and nothing after. A few things to check: Compare what landed with what Wiz shows. Run this over one full pull window, and swap in your index, sourcetype and vulnerability ID field: index=<your_wiz_index> sourcetype=<your_wiz_vuln_sourcetype> earliest=-24h | stats count dc(<vuln_id_field>) as unique_vulns by severity If unique_vulns sits on a round number while the Wiz console shows more, the pull is getting cut off. Find out where the add-on writes its own log. It may not match source=*wiz* in _internal, which would explain the empty result. Check $SPLUNK_HOME/var/log/splunk/ for a Wiz-named file, then run: index=_internal source=*wiz* | stats count latest(_time) as last_seen by source | convert ctime(last_seen) If the add-on has a log-level setting, set it to DEBUG for one run and see whether the last request still reported more pages, and whether the run ended with an error or a timeout. The four inputs probably share one Wiz service account, so they share its API quota. Stagger their start times, and make sure each run finishes before its next interval, so two pulls of the same severity never overlap. If DEBUG shows it stopping while Wiz still reports more pages, that's worth raising with the add-on maintainer, along with the exact counts from both sides.
... View more