Skip to content

Conversation

@simonabadoiu
Copy link
Contributor

Summary

Adds a new FAQ entry in the Errors & Troubleshooting section explaining why page content might be missing and when to use networkidle0 vs networkidle2.

Changes

  • Added new FAQ: "Why is my page content missing or incomplete?"
  • Explains the difference between networkidle0 and networkidle2 with a clear use-case table
  • Includes REST API example
  • Links to existing timeouts reference for deeper details

Why

The timeout/waitUntil documentation already exists in the timeouts reference, but users often look in the FAQ first when troubleshooting. This surfaces that information where users are most likely to find it.

@github-actions
Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/browser-rendering/ @mchenco, @cloudflare/pcx-technical-writing, @celso, @kathayl, @ToriLindsay

@github-actions
Copy link
Contributor

github-actions bot commented Jan 29, 2026

@simonabadoiu simonabadoiu force-pushed the sbadoiu/faq-networkidle-timeouts branch 4 times, most recently from d2921a6 to 0036d1d Compare January 29, 2026 17:01
Adds a new FAQ entry in Errors & Troubleshooting section explaining:
- Why content might be missing (JS-heavy pages, SPAs)
- When to use networkidle0 vs networkidle2
- Example REST API usage
- Additional troubleshooting tips

This surfaces existing timeout documentation in the FAQ for better
discoverability when users search for help with incomplete renders.
@simonabadoiu simonabadoiu force-pushed the sbadoiu/faq-networkidle-timeouts branch from 0036d1d to bec733e Compare January 29, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants