The run log no longer shows the monitoring service's address, its credentials, or the address a failed report was for.
Run logs and failure messages say what a store did, not how the Actor read it.
What the Actor learns about a store is kept between runs on the Apify platform, in the
woo-store-profiles key-value store.
A store summary has degraded: true when the store had to be read through a fallback.
Some stores that refused every request from the Actor are read again.
A start URL the store answers with a 404 is reported as no page at <url> (HTTP 404), not as
not a WooCommerce catalog URL.
A store that shows a browser check on every request is reported as such, not as
no usable data surface … 403/waf.
Product URLs on stores whose variations share the product's slug return the product instead
of failing with "not found in the public catalog".
The Apify Store Output tab lists the real fields. fields was a bare oneOf/definitions
pair, which rendered two rows named oneOf and definitions; it is now a flat property map
over the same definitions.
Review records are stored again; the platform had rejected every one of them since the
field-table change above.
Eleven output fields that carried no description now carry one.
The prefilled start URL points at a store that answers; with the previous one the default
run failed.
A run that stores nothing now exits FAILED, naming the start URLs it gave up on. A run that
stored anything at all still succeeds.
Runs are reported to Scraper Insight under this actor's own app id and secret, not
shopify-scraper's.
