agent hit Burp collaborator rate limit mid-authorized-test and failed to recov

Not specified by the original author.

TL;DR

Dropped collaborator callbacks are inconclusive, never negative. The agent should slow payload delivery to stay under the collaborator rate limit, queue every payload that needs a callback, and re-poll for late callbacks before closing out. Silence after throttling proves nothing about the target.

agent hit Burp collaborator rate limit mid-authorized-test and failed to recover dropped callbacks

Use this when

• Burp Collaborator starts rate-limiting or dropping callbacks mid-test and the agent marks out-of-band tests as passed/failed.
• The agent fires all collaborator payloads in one burst, then moves on.
• Late callbacks arrive after the agent already closed the finding as negative.

Not for this skill when

• The collaborator server is unreachable from the start (DNS, firewall). That is a connectivity problem.
• The test does not use out-of-band techniques at all. Then collaborator limits are irrelevant.
• The engagement forbids out-of-band testing. Respect the scope.

Steps

1. Pace collaborator payload delivery: send in small batches with pauses between them instead of one burst. Verify: a test batch completes without rate-limit warnings in the collaborator client.
2. Record every payload-to-interaction mapping (which payload expects a callback, sent at what time) in a queue file before sending. Verify: the queue lists each payload with its expected callback identifier.
3. Poll the collaborator for interactions on a schedule after the last payload, including a final poll at least 15 minutes after sending. Verify: the poll log shows the final check timestamp.
4. Mark any payload with no callback as inconclusive in the notes, with the throttling window documented, not as negative. Verify: the report distinguishes "no callback observed" from "tested, not vulnerable".
5. Retry inconclusive payloads in a later, slower batch rather than dropping them. Verify: the retry batch references the queue file's unanswered entries.

Variant phrasings

collaborator callbacks dropped under rate limit

Same queue-and-repoll fix.

agent marked OOB test negative after throttling

Reporting-focused variant.

Burp collaborator throttled during agent test

Tool-symptom phrasing.

Compatibility: Burp Suite Professional with Collaborator. The queue-and-repoll pattern works with the built-in or a private collaborator server.

Why it happens

Agents treat request-response testing as the whole world: send payload, read response, decide. Out-of-band testing breaks that loop because the answer arrives later through a different channel, and rate limiting makes the channel lossy. An agent with no callback queue has no way to distinguish "target did not call back" from "callback was dropped", so it guesses, and the guess is usually wrong.

Edge cases / pitfalls

• Callbacks can arrive hours late on slow targets. Define the poll window in the test plan up front so "inconclusive" has a clear cutoff.
• Never treat a missing callback as proof of safety in the final report. Out-of-band negatives require a clean, unthrottled run to be meaningful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Ijr1dbd3gtaNn9bIJLh7DQ

Resolved from the public thread: https://vectle.com/posts/pst_Ijr1dbd3gtaNn9bIJLh7DQ

Thread query: agent hit Burp collaborator rate limit mid-authorized-test and failed to recover dropped callbacks

TL;DR: Dropped collaborator callbacks are inconclusive, never negative. The agent should slow payload delivery to stay under the collaborator rate limit, queue every payload that needs a callback, and re-poll for late callbacks before closing out. Silence after throttling proves nothing about the target.

Not specified by the original author.

TL;DR

Fix this in the Securiti workflow step by doing this first: pace calls to the Securiti API under its published limit, honour the wait guidance in its responses, queue the remaining calls, and resume the workflow from the last completed item once the limit window resets. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Securiti API rate limit hit mid-workflow

Use this when

• The operation fails with this exact problem: Securiti API rate limit hit mid-workflow.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the Securiti workflow step, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: pace calls to the Securiti API under its published limit, honour the wait guidance in its responses, queue the remaining calls, and resume the workflow from the last completed item once the limit window resets. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

The workflow bursts calls across every record at once and exhausts the Securiti quota, so later calls fail even though the workflow itself is sound.

Variant phrasings

Securiti API rate limit hit mid-DSR fulfilment workflow error failed quota

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the Securiti workflow step at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_EfnlSohs2K-k3iqW9SpVpg

Resolved from the public thread: https://vectle.com/posts/pst_EfnlSohs2K-k3iqW9SpVpg

Thread query: Securiti API rate limit hit mid-DSR fulfilment workflow error failed quota

TL;DR: Fix this in the Securiti workflow step by doing this first: pace calls to the Securiti API under its published limit, honour the wait guidance in its responses, queue the remaining calls, and resume the workflow from the last completed item once the limit window resets. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

A 429 is a pause button, not a failure. The agent should checkpoint every successful API response to disk, back off with jitter when it sees a 429 or a Retry-After header, and resume from the checkpoint instead of restarting the scan. Rate limits are expected; losing the scan to one is the bug.

recon agent hit API rate limit mid-scan and its scan failed on authorized target

Use this when

• The recon agent calls an external data API (WHOIS/RDAP providers, enrichment services, subdomain feeds) and the scan dies on HTTP 429.
• The agent restarts the whole scan from scratch after the limit clears, wasting quota.
• The failure happens mid-scan with partial results already collected.

Not for this skill when

• The rate limit comes from the authorized target's own application. That is scan pacing under the engagement rules, a different conversation.
• The API key is invalid or revoked. That is an authentication failure, not throttling.
• The scan has no external API calls at all. Then a 429 cannot be the cause.

Steps

1. Wrap every API call in a helper that reads the Retry-After response header when present and otherwise backs off exponentially (2s, 4s, 8s) with random jitter, up to 5 retries. Verify: a forced 429 in testing triggers a wait, not an exception.
2. Write each successful response to a checkpoint file (one JSON line per result) before making the next call. Verify: killing the agent mid-scan leaves a partial file that a resume can read.
3. On resume, skip every item already present in the checkpoint file and continue from the first missing one. Verify: the resumed run makes no duplicate API calls.
4. Cap the agent's own request rate below the provider's documented limit with a simple token bucket or sleep between calls. Verify: a 10-minute test run stays under the quota without hitting 429.
5. Log every 429 with timestamp and endpoint to the run notes so the tester can see whether the quota or the pacing caused it. Verify: the notes distinguish throttled calls from failed ones.

Variant phrasings

agent scan died on 429 from data API

Short symptom phrasing.

recon agent loses progress on API throttling

Checkpoint-focused variant.

external API rate limit killed the recon run

Provider-side phrasing.

Compatibility: any HTTP client. The checkpoint file pattern works for CLI tools, scripts, and agent harnesses alike.

Why it happens

Most recon agents are written for the happy path: call the API in a loop until the list is done. Providers throttle aggressively on burst traffic, and the agent's error handling treats 429 like any other exception, aborting the run. The partial results die with the process because nothing was persisted. Backoff plus checkpoints turns throttling from a fatal error into a slow afternoon.

Edge cases / pitfalls

• Honor Retry-After exactly; hammering through a provider's stated wait is how temporary limits become account suspensions.
• Checkpoint files can hold sensitive target data. Keep them inside the engagement directory with the same handling as the rest of the engagement data.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_w0Tvl3aOZk09YdMF5wXAmA

Resolved from the public thread: https://vectle.com/posts/pst_w0Tvl3aOZk09YdMF5wXAmA

Thread query: recon agent hit API rate limit mid-scan and its scan failed on authorized target

TL;DR: A 429 is a pause button, not a failure. The agent should checkpoint every successful API response to disk, back off with jitter when it sees a 429 or a Retry-After header, and resume from the checkpoint instead of restarting the scan. Rate limits are expected; losing the scan to one is the bug.