ScreenshotOne can now catch more incomplete page loads when you use the fail_if_request_failed option.
Previously, the option detected a matching resource when the browser reported a network-level failure. However, a server or CDN can return an HTTP error response while the browser still considers the network request complete. In that case, a screenshot could be rendered with a missing stylesheet, image, or script.
Now, a rendering request fails when a matching resource either fails at the browser or network level or returns an HTTP status code from 400 through 599.
For example, if a required CSS file from example.com fails to load, the website may be rendered without its layout and styles. You can detect this by matching its CSS requests:
fail_if_request_failed=*example.com/*.css*ScreenshotOne returns the matched_failed_request error instead of the incorrectly rendered screenshot when the pattern matches a failed CSS request. Your integration can retry the API request and treat repeated failures as a persistent website problem. ScreenshotOne does not perform this retry automatically.
Read more about matching failed requests in the documentation.
