Skip to content

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

Merged
emilyrohrbough merged 2 commits intomainfrom
cloud-config-updates
Jan 31, 2026
Merged

improve docs for run complete delay and run time settings#6361
emilyrohrbough merged 2 commits intomainfrom
cloud-config-updates

Conversation

@emilyrohrbough
Copy link
Member

No description provided.

@cypress
Copy link

cypress bot commented Jan 30, 2026

cypress-documentation    Run #882

Run Properties:  status check passed Passed #882  •  git commit 267590e186: feedback
Project cypress-documentation
Branch Review cloud-config-updates
Run status status check passed Passed #882
Run duration 06m 14s
Commit git commit 267590e186: feedback
Committer Emily Rohrbough
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 314
View all changes introduced in this branch ↗︎
UI Coverage  10.84%
  Untested elements 2528  
  Tested elements 3  
Accessibility  96.88%
  Failed rules  1 critical   3 serious   4 moderate   0 minor
  Failed elements 28  

Comment on lines 217 to 226
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 lengthen the timeout if your tests or CI need
more time to send results, or shorten it if you want faster feedback when a run has
stopped sending data.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emilyrohrbough I would say that the use case is more often someone wanting to set it shorter so that their runs can quickly time out. If someone needs to set it higher than 90 minutes, they should be looking at other ways to optimize their run honestly as that's a really gracious amount of time.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point

@emilyrohrbough emilyrohrbough merged commit fc4dbf6 into main Jan 31, 2026
11 checks passed
@emilyrohrbough emilyrohrbough deleted the cloud-config-updates branch January 31, 2026 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants