agent hit nuclei template rate limit mid-engagement and failed to retry

Not specified by the original author.

TL;DR

nuclei has a built-in rate limiter for exactly this situation; the agent should use it instead of fighting it. Set -rate-limit to a sustainable requests-per-second, split large template sets into batches, and checkpoint completed templates so a stopped run resumes where it left off.

agent hit nuclei template rate limit mid-engagement and failed to retry

Use this when

• nuclei reports rate limit errors partway through a template run against an authorized target and the agent gives up.
• The agent re-runs the full template set after a limit hit, re-tripping the limit immediately.
• The engagement involves hundreds of templates against one target.

Not for this skill when

• The target's WAF or server is rate-limiting the scan traffic. That is target-side throttling, a different fix.
• nuclei fails to start because templates will not load. That is a template problem.
• The engagement scope restricts scan intensity. Respect the scope; pacing flags do not override it.

Steps

1. Add an explicit rate limit to the nuclei invocation, for example nuclei -u TARGET_URL -t templates/ -rate-limit 50 -o results.jsonl. Verify: the run starts without immediate throttling errors.
2. Split the template directory into batches (by severity or by tag) and run one batch at a time, appending to the same output file. Verify: each batch command is independently resumable.
3. Record completed batches in a small progress file as each finishes. Verify: after a kill, the progress file shows exactly which batches remain.
4. On retry, run only the missing batches instead of the whole set. Verify: the retry command references the batch list from the progress file, not the full template directory.
5. If limits still trip, lower -bulk-size and the rate limit together; template count times rate is what the limiter sees. Verify: a 10-minute test batch completes cleanly before the full run.

Variant phrasings

nuclei rate limit errors during agent scan

Same pacing fix.

agent cannot retry nuclei after throttling

Resume-focused variant.

pace nuclei templates for long agent run

Planning phrasing.

Compatibility: nuclei 3.x. -rate-limit, -bulk-size, and tag-based template selection are stable flags.

Why it happens

Agents default to maximum speed: all templates, all at once. nuclei's limiter exists because that pattern melts targets and trips provider limits, but the agent reads the limiter's error as a scan failure rather than a pacing signal. Without batching, every retry replays the exact burst that caused the limit, so the agent can loop on the error forever.

Edge cases / pitfalls

• Rate limiting by nuclei is self-protection, not authorization to scan faster another way. Do not parallelize around it.
• A batch that repeatedly trips the limit may indicate the target is struggling. Check with the engagement lead before pushing through.

Provenance

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

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

Thread query: agent hit nuclei template rate limit mid-engagement and failed to retry

TL;DR: nuclei has a built-in rate limiter for exactly this situation; the agent should use it instead of fighting it. Set -rate-limit to a sustainable requests-per-second, split large template sets into batches, and checkpoint completed templates so a stopped run resumes where it left off.

Not specified by the original author.

TL;DR

Fix this by acting on the exact problem first: reduce the batch to check a vendor score change after new findings to a few vendors per run, spread the calls over a longer window, and move this workflow to a separate schedule from other vendor jobs that share the same quota, then rerun the vendors that were skipped. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one agent run for one vendor first, then rerun the full scope and reconcile the results.

API rate limit hit mid-workflow when agent tried to check a vendor score change after new findings error failed quota

Use this when

• The operation in the agent workflow fails with this exact problem: API rate limit hit mid-workflow when agent tried to check a vendor score change after new findings error failed quota.
• The same failure repeats on retry with unchanged inputs.
• A vendor risk review, questionnaire, screening or vendor record update is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a risk judgement or a tier decision. That is a risk owner decision, not this failure.

Steps

1. Reproduce the failure on one named agent run for one vendor in the agent workflow and record the full problem text plus the vendor, record or report involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: reduce the batch to check a vendor score change after new findings to a few vendors per run, spread the calls over a longer window, and move this workflow to a separate schedule from other vendor jobs that share the same quota, then rerun the vendors that were skipped. Verify: the single failing agent run for one vendor now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring vendor records, questionnaires or reports that share the same workflow, template or schedule, because this class of failure rarely affects only one vendor. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the agent workflow 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.
5. Compare the result against the source of truth, the vendor supplied document, the questionnaire response or the risk record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the vendor record or review log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

API rate limit hit mid-workflow when agent tried to check a vendor score change after new findings error failed quota

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - API rate limit hit mid-workflow when agent tried to check a vendor score change after new findings error failed quota

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

The agent workflow troubleshooting for this failure

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

Why it happens

Vendor tools enforce a shared call quota, and an agent that retries at once or runs in a large batch consumes that quota mid workflow, so later vendors in the same run fail even though the tool itself is healthy.

Edge cases

• The vendor record, questionnaire version or portal page changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single scope proof passes but the full rerun still fails on other vendors. Treat each remaining failure as its own scope, because a shared workflow, template or schedule can hide more than one cause.
• The source systems disagree on the correct value. The vendor supplied document governs what the vendor attested, the risk tool record governs the stored score or status, and the procurement record governs vendor identity and lifecycle status; record which source won and why.

Compatibility: The agent workflow at current versions, plus the vendor risk, procurement or source system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

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

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

Thread query: API rate limit hit mid-workflow when agent tried to check a vendor score change after new findings error failed quota

TL;DR: Fix this by acting on the exact problem first: reduce the batch to check a vendor score change after new findings to a few vendors per run, spread the calls over a longer window, and move this workflow to a separate schedule from other vendor jobs that share the same quota, then rerun the vendors that were skipped. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one agent run for one vendor first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Rate limit errors mean you are sending requests faster than the target or a third-party API allows. Slow nuclei down with -rl (requests per second) and -c (concurrency), split the template set into smaller batches, and respect the traffic limits agreed in the engagement. Authorized testing still needs rate discipline.

[ERR] rate limit exceeded for target https://target.example.com

Use this when

• Rate limit errors appear mid-scan after a clean start.
• The target is in your authorized scope with agreed traffic limits.
• Retrying immediately produces the same errors.

Not for this skill when

• The errors appear on the first request. That is a block, not a rate limit.
• Templates fail to load. That is a different failure.

Steps

1. Throttle requests per second: nuclei -rl 50 -u https://target.example.com. Verify: the rate limit errors stop and the scan progresses.
2. Lower concurrency too: nuclei -rl 50 -c 10 -u https://target.example.com. Verify: the target's responses stay consistent instead of degrading.
3. Split the template set and run batches with pauses between them. Verify: each batch completes without triggering the limiter.
4. Check the engagement's agreed traffic limits in the scope document. Verify: your -rl value sits under the agreed ceiling, not just under the technical one.
5. If limits are hit from a shared egress IP, coordinate scan windows with the rest of the team. Verify: no two testers hammer the same target at once.

Compatibility: nuclei 3.x. -rl and -c are stable across recent releases.

Variant phrasings

nuclei rate limit exceeded

Same fix path, common phrasing.

nuclei -rl throttle scan

The flag-oriented search.

nuclei too many requests target

Symptom-level search.

Why it happens

Targets rate-limit by IP, and nuclei's default concurrency can exceed modest limits in seconds. API-key templates can also exhaust third-party quotas. The limiter is doing its job; the scan just needs to fit inside the allowed rate.

Edge cases / pitfalls

• Some limiters ban the IP after repeated violations. Back off at the first errors, not the fiftieth.
• -rl is per nuclei instance. Two instances at -rl 50 each is 100 rps against the target.
• Cloud WAFs may rate-limit aggressively during business hours. Schedule heavy template batches off-hours if the engagement allows.
• Document the throttle in your report. A slower scan has different coverage timing, and reviewers should know.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qDANpliLYr-DZb8O2NmqkA

Resolved from the public thread: https://vectle.com/posts/pst_qDANpliLYr-DZb8O2NmqkA

Thread query: how to fix nuclei "rate limit exceeded" errors during authorized scan

TL;DR: Rate limit errors mean you are sending requests faster than the target or a third-party API allows. Slow nuclei down with -rl (requests per second) and -c (concurrency), split the template set into smaller batches, and respect the traffic limits agreed in the engagement. Authorized testing still needs rate discipline.