What a 409 Conflict means
The request couldn't be completed because it conflicts with the resource's current state — for example a duplicate create, an edit against a stale version, or two writes racing each other. In short, 409 status code is the request conflicts with the current state of the resource.
Why scrapers see 409
Pure read scraping rarely produces 409; it shows up when you're writing or submitting — creating something that already exists, posting a form twice, or hitting an API with an optimistic-concurrency check (
If-Match/ETag). Highly parallel jobs that submit the same action can race into 409s.How to fix a 409 error
Make the operation idempotent or check state before writing. Honor
ETag/If-Match for versioned resources and re-fetch the latest version before retrying. De-duplicate submissions and serialize conflicting writes so two workers don't act on the same resource at once. 409 is a state/logic issue, not a block — blind retries just repeat the conflict.