# vendor portal scraper agent blocked by cloudflare challenge after 10 pages: how to fix it

Rapid page loads trigger the bot challenge. Slow the crawl, randomize delays, and when the challenge appears, back off for an extended period instead of hammering through it.

```text
vendor portal scraper agent blocked by cloudflare challenge after 10 pages
```

## When to use this skill
- Scraper hits a Cloudflare challenge after several pages
- Challenge appears partway through a run

## When not to use this skill
- IP is banned outright (a harder block)
- Challenge appears on the first page (a stricter setup)

## Tool compatibility
Agent scraper bot-challenge handling. Related area: browser automation.

Related area: proposal automation and agent-assisted RFP workflows.

Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with scraper hits a Cloudflare challenge after several pages, start at step 1 below.
- If instead iP is banned outright (a harder block), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Slow the crawl rate

```
Add multi-second delays between page loads.
```
Expected: Expected: pages load without triggering the challenge.

### 2. Randomize the delays

```
Vary each delay so the pattern is not mechanical.
```
Expected: Expected: traffic looks less automated.

### 3. Back off on challenge

```
When the challenge page appears, pause the run for 15 minutes.
```
Expected: Expected: challenge clears on resume.

### 4. Resume at a slower rate

```
Continue the scrape at half the previous speed.
```
Expected: Expected: remaining pages complete.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (slow the crawl rate): Expected: expected: pages load without triggering the challenge.
- Step 2 (randomize the delays): Expected: expected: traffic looks less automated.
- Step 3 (back off on challenge): Expected: expected: challenge clears on resume.
- Step 4 (resume at a slower rate): Expected: expected: remaining pages complete.

## Quick recap
1. Slow the crawl rate
2. Randomize the delays
3. Back off on challenge
4. Resume at a slower rate

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### agent cloudflare challenge scrape
Slow down and back off. If this matches what you saw, the steps above apply as written.

### vendor portal scraper blocked challenge
Extended pause clears it. If this matches what you saw, the steps above apply as written.

## Why it happens
Challenge systems score request velocity, and a scraper running at full speed trips the bot threshold fast. Hammering the challenge page raises the score further; a real pause lets it decay.

## Edge cases
- Check the portal terms before scraping; some prohibit it entirely
- Use official APIs or data exports where the portal offers them
- Scrape off peak when the portal is less sensitive

## Provenance

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