Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Timeout

The timeout is the maximum time, in seconds, that BugBug spends on one step. During this time BugBug waits for the step's waiting conditions, runs the step, and retries it if it doesn't pass, for example an assertion that is checked again every 1.5 seconds. If the step still doesn't pass when the timeout ends, the test fails.

The default timeout is 30 seconds in local runs and 60 seconds in cloud runs. The maximum is 300 seconds.

How the timeout is used

  • It starts after the delay. If the step has a delay, the timeout starts counting when the delay ends.

  • Part of it is for waiting conditions. After 70% of the timeout (for timeouts up to 10 seconds) or 50% (for longer timeouts), BugBug skips optional waiting conditions that still aren't met and runs the step. With the defaults, that's after 15 seconds locally and 30 seconds in the cloud. See How a step waits.

  • A step that passes doesn't wait for the timeout. The timeout is only a limit; BugBug continues as soon as the step succeeds.

Configure global timeout

Set the timeout for local and cloud runs separately in Project settings → General.

  • Increase it if your page is slow or tests fail in the cloud. See Cloud tests sometimes failing.

  • Decrease it if you don't want to wait that long for a failed test result.

Timeout settings for local and cloud runs in project settings

Change timeout for individual steps

You can set a different timeout, up to 300 seconds, for one step in the step's settings. It replaces the project timeout for this step, in local and cloud runs. Leave it empty to use the project timeout.

Timeout field in the step settings

In YAML the field is execution.run_timeout, and in the API and MCP runTimeout, both in seconds:

Raise the timeout for the slow step only, not for the whole project. A longer project timeout makes every failing step take longer to fail.

Maximum test duration in the cloud

Besides the step timeout, a single test running in the cloud has a maximum duration, counted from the start of the test run:

Plan
Maximum duration of a single cloud test

Core

10 minutes

Pro

15 minutes

Business and trial

30 minutes

When a cloud test runs longer, it fails with SINGLE_TEST_TIME_EXCEEDED. Local runs don't have this limit. If your tests get close to the limit, split them into shorter tests and run them in a suite.

Error code
Meaning

FAILED_WAITING_CONDITIONS

A required waiting condition wasn't met before the timeout.

ELEMENT_DOES_NOT_EXIST

No element matched the selector before the timeout.

ASSERT_FAILED

The assertion didn't pass before the timeout.

TIMEOUT

The step didn't finish before the timeout, for example a slow page or long JavaScript.

SINGLE_TEST_TIME_EXCEEDED

A cloud test ran longer than the maximum test duration of your plan.

See all error codes.

Last updated

Was this helpful?