v0.1.29 — Scrape Error Reporting & Retry UI
Scrape Error Reporting & Retry UI
Version: 0.1.29
This release introduces transparent error reporting and manual retry controls for failed product scrapes. Previously, a scrape failure would result in a product row with missing data and no indication of why. Now, failures are surfaced clearly in the dashboard with enough context to understand what went wrong and act on it.
Error States on the Dashboard
When a scrape fails, the affected product row in the dashboard enters an error state. This is shown inline so it is immediately visible alongside successful results — there is no need to navigate to a separate error log.
Failure Types
| Failure Type | Description |
|---|---|
| 403 Blocked | The target site rejected the scrape request with an HTTP 403 response |
| Timeout | The scrape did not complete within the allowed time window |
| No reviews found | The page loaded successfully but contained no reviews to extract |
| Parsing error | The page was fetched but its HTML structure could not be parsed correctly |
Error Detail Tooltip
Each failed product row includes a tooltip that exposes:
- HTTP status code — the raw response code returned by the target site (e.g.
403,504) - Error message — the specific error encountered during the scrape
- robots.txt block — whether the failure was due to a
robots.txtexclusion rule
This detail is useful for distinguishing transient failures (timeouts, rate limits) from permanent blocks (robots.txt, hard 403s), helping you decide whether a retry is likely to succeed.
Manual Retry
Failed products can be re-scraped individually without triggering a full directory crawl. The retry control is available directly on the failed product row.
When to Retry
- Timeout — likely worth retrying; may have been a momentary server-side issue
- No reviews found — worth retrying if the product listing was recently updated
- Parsing error — retry after a page structure change has been handled
- 403 / robots.txt block — retrying is unlikely to succeed without a change in scrape configuration; review the error detail before retrying
Notes
- Retry is scoped to a single product — it does not re-crawl the parent directory or affect other products in the same run.
- Error state and tooltip data persist until a successful scrape or a new run is initiated.