Skip to content

improve docs for run complete delay and run time settings #6361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
emilyrohrbough merged 2 commits into from
Jan 31, 2026
Merged

improve docs for run complete delay and run time settings #6361

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
96b3d8c
improve docs for run complete delay and run time settings
emilyrohrbough Jan 30, 2026
267590e
feedback
emilyrohrbough Jan 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 32 additions & 6 deletions docs/cloud/account-management/projects.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,8 +187,16 @@ and [Auto Cancellation](/cloud/features/smart-orchestration/run-cancellation) gu

#### Run completion delay

You can edit the number of seconds that a run will wait for new groups to join
before transitioning to 'completed'.
Control how long the Cypress Cloud should wait for new groups to join a run before transitioning a run to a _completed_ status with the **Run completion delay** . This gives your test groups a grace period to join an existing run before the run is considered complete.

Use run completion delay when you have a distributed test setup where test groups might
not all start simultaneously. For example:

- CI jobs that might start at slightly different times
- [Parallelization](/cloud/features/smart-orchestration/parallelization) across multiple machines
- Flaky network conditions that might delay some test groups from connecting

The default is **60 seconds**. Increasing this value gives your test groups more time to join the run; decreasing it will make runs complete faster when no new groups are joining.

See our
[Parallelization guide](/cloud/features/smart-orchestration/parallelization#Run-completion-delay)
Expand All @@ -201,17 +209,35 @@ to learn more.

### Run Timeout

You can edit the number of minutes that Cloud will wait to receive a signal from the run before being set to
'Timed Out'. The default is 90 minutes. Valid timeout values are between 5 and 300 minutes.
**Run timeout** is the number of minutes that Cypress Cloud will
wait to receive a signal from a run before marking the spec and run as **Timed Out**.
This is the maximum time Cypress Cloud will wait for activity from your tests before
considering them hung or failed.

Use run timeout when you have long-running tests that might exceed the default. For
example:

You can lengthen the timeout if you are experiencing runs that have passing / failing tests but are not being
captured by Cloud due to a timeout. You can shorten the timeout if you need faster feedback.
- Very long-running end-to-end tests
- Tests that include operations that take significant time (such as large file uploads)
- Operations with unpredictable completion times

The default is **90 minutes**. You can shorten this for faster feedback when a run has stopped sending data.

<DocsImage
src="/img/cloud/projects/run-timeout-setting.jpg"
alt="Run timeout setting"
/>

#### Run completion delay vs. Run timeout

These settings work together to balance giving your tests enough time to complete
while not waiting indefinitely for runs that have failed or hung:

- **Run completion delay** (seconds): How long to wait for new test groups to join
after all currently known groups complete. Applies only during that waiting period.
- **Run timeout** (minutes): How long to wait for any activity from a run before
marking it timed out. Applies throughout the entire run.

### Transfer ownership

#### Transfer project to other user or organization
Expand Down