Improved error handling when networking fails

We have improved error handling for network failures. Now, we ensure screenshot rendering fails instead of returning an error image.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

For a short period of time, there was a temporary and sporadic issue with the screenshot rendering. It was reported by many customers, but it was hard to reproduce and fix.

The issue was that the screenshot rendering was failing because of a networking issue, but screenshots were still returned and returned an error image like:

A default browser error image

It was a temporary and occasional issue, but it was super annoying for many customers.

After a thorough investigation, applying the best practices on navigation error handling with Puppeteer, and a few more improvements, I found the root cause, managed to reproduce it and fixed it.

Now, the screenshot rendering will fail instead of returning an error image. And you can safely retry such requests. Also, we will be notified now, cause the uptime monitor will fail too.

Super sorry for the inconvenience! But hopes it won’t be repeated again.

If you encounter any other issues, please, reach out at support@screenshotone.com.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Clearer usage limits and upgrade actions

Clearer usage limits and upgrade actions

Clearer usage limits, more links to Billing, and easier plan comparison.

Read more

1 min read

Transfer organization ownership

Transfer organization ownership

From today, you can transfer organization ownership to another user.

Read more

1 min read

Multiple notification recipients

Multiple notification recipients

Add multiple dedicated email recipients for usage limit notifications.

Read more

1 min read

Automate website screenshots

Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.