7.7Timeouts

A timeout is the longest time obsrvly waits before it gives up. A browser monitor has two kinds.

Timeout	What it limits	Default	Where to set it
Check timeout	The whole script. All steps share it.	10 seconds in the dashboard. 30 seconds through the API if you leave out `timeoutMs`.	Dashboard: timeout, in seconds. API: `timeoutMs`, in milliseconds. Up to 120 seconds.
Step timeout	How long one step waits for its element or its page.	10 seconds.	API only: `timeout_ms` on the step, in milliseconds. Not on `goto`.

The check timeout can be at most 120 seconds. A larger value is cut to 120 seconds without a warning.
A step never gets more time than is left of the check timeout. With the dashboard default of 10 seconds, all steps share those 10 seconds. Raise timeout for longer scripts.
goto always waits up to 10 seconds, or less if the check is nearly out of time.
Write timeout_ms as a number, such as "timeout_ms": 15000. Values of 0 or less use the 10-second default. Values above 120000 are cut to 120000.
Without a script, the single page load can use the whole check timeout.

Messages you may see when time runs out:

Message	What to do
`step 3 (click): script exceeded its 10000ms timeout`	The script used up the check timeout before this step started. Raise timeout, or shorten the script.
`timed out after 10 s`	The whole check took longer than its timeout. Raise timeout, or split the task.
A step's error says it timed out	The element did not appear in time. Check the selector. If the page is slow, give the step more time with `timeout_ms` (API).