What triggers Cloudflare 1015
Site owners write rate-limiting rules in their Cloudflare dashboard — essentially "if one IP makes more than N requests in M seconds against path X, block it for T minutes." When your scraper crosses that line, Cloudflare's edge serves the 1015 page instead of passing the request along. Typical rules look like 10 requests per 10 seconds for a login page, 100 per minute for catalog pages, or tighter limits on search and pricing endpoints. The ray ID on the error page identifies your specific blocked request — you could hand it to the site owner if you have a legitimate reason, but for unaffiliated scraping that isn't an option.
How to recover from a 1015
The block is tied to your IP and lasts a set amount of time. Switching to a different IP through proxy rotation (cycling requests across many addresses) clears it right away. The clean approach is to watch the response body for the 1015 marker, flag the current IP as "cooling off" for the block duration (the error message often tells you how long), and send the next requests through a different IP. If you don't rotate proxies, your only choice is to wait — the block usually clears in 5–60 minutes depending on the rule. Note that hammering the same IP during the cooldown extends the block on many setups.
How to avoid 1015 in the first place
Slow down how often each IP hits the site. The thresholds that trigger 1015 are often around 100+ requests per minute per IP, so staying well under that on every IP in your pool keeps you safe. Spread the work across a larger proxy pool so each individual IP looks like ordinary traffic. Add jitter (small random delays) between requests, since perfectly evenly-spaced requests are exactly the pattern rate-limiting rules look for. And cache: if you grabbed a page recently, don't fetch it again. Most 1015 problems come from scrapers that pile too many simultaneous requests onto a single proxy without measuring the rate.