Skip to main content
No Result Found

Error - Network idle timeout

Learn how to fix errors related to network idle timeouts in Percy

This occurs when all requests are not finished within the network idle timeout (30 seconds) during the asset discovery phase after the page has loaded. This can happen if there are a large number of network requests on your page or if your CI has limited resources.

Try these solutions to resolve this error:

Solution 1:

If your page has a large number of requests that might take more than 30 seconds, try increasing the network idle timeout using PERCY_NETWORK_IDLE_WAIT_TIMEOUT. For more information, refer to the Set environment variables page.

Solution 2:

If you are running Percy inside a CI environment, try increasing the CI resource where the Percy CLI is running.

Solution 3:

  • Check network logs for any particular asset that is taking time to load. This could be causing the issue. SVGs and video content generally take longer time than usual to resolve.
  • If these assets are causing the issue, consider using the domTransformation option to allow Percy to remove these assets from the DOM when the page is rendered. Learn more on DOM transformation.

Reference Topic

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked





Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked





Thank you for your valuable feedback!

Talk to an Expert
Download Copy Check Circle