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
@@ -17,7 +17,7 @@ Each timer controls a specific part of the rendering lifecycle — from page loa
17
17
|`goToOptions.waitUntil`| Waits for an event to fire. load (default) — waits for the full load event.domcontentloaded — waits for the DOMContentLoaded event.networkidle0 — waits until there are no more than 0 network connections for at least 500 ms.networkidle2 — waits until there are no more than 2 network connections for at least 500 ms. | Load is the default | — |
18
18
|`waitForSelector`| Time to wait for a specific element (any CSS selector) to appear on the page. | null | 60 s |
19
19
|`waitForTimeout`| After the page has loaded, waits an additional fixed time before proceeding. | null | 60 s |
20
-
|`actionTimeout`|How long to wait for the action itself (screenshot, PDF, scrape, etc.) to complete after loading finishes.| null | 5 min |
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