You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/browser-rendering/reference/timeouts.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Each timer controls a specific part of the rendering lifecycle — from page loa
16
16
|`goToOptions.timeout`| Time to wait for the page to load before timeout. | 30 s | 60 s |
17
17
|`goToOptions.waitUntil`| Time until page load considered complete: <br />`load` = full page load, including resources, like images and stylesheets. <br />`Event.domcontentloaded` = waits until the DOM content has been fully loaded, fires before the page `load` event. <br />`Event.networkidle0` = there are no active network connections for at least 500 ms. <br />`Event.networkidle2` = there are no more than two active network connections for at least 500 ms. | — | — |
18
18
|`waitForSelector`| Time to wait for a specific element (any CSS selector) to appear on the page. | null | 60 s |
19
-
|`waitForTimeout`| Additional amount of time to wait after the page has loaded to proceed with actions. | null |60 s|
19
+
|`waitForTimeout`| Additional amount of time to wait after the page has loaded to proceed with actions. | null |5 min|
20
20
|`actionTimeout`| Time to wait for the action itself (for example: a screenshot, PDF, or scrape) to complete after the page has loaded. | null | 5 min |
21
21
|`PDFOptions.timeout`| Same as `actionTimeout`, but only applies to the [/pdf endpoint](/browser-rendering/rest-api/pdf-endpoint/). | 30 s | 5 min |
0 commit comments