> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/troubleshooting/cloud-tests-sometimes-failing.md).

# Cloud tests sometimes failing

Discover effective troubleshooting techniques for resolving intermittent cloud test failures. BugBug's comprehensive guide helps you tackle testing challenges.

By default, BugBug will attempt to run a test step for 30 seconds locally and 60 seconds in the cloud. If BugBug is not able to perform a test step in this amount of time, it will mark the step as failed - this is called a *timeout*.

If your local tests are stable, but only cloud tests are sometimes failing randomly, most likely it is caused by the fact, that BugBug cloud virtual machines are not as fast as your own computer. It may take longer for the page to process in the cloud.

To prevent this you can **increase the timeout of cloud runs**:

1. Go to project settings
2. Change the "Cloud runs timeout" to a higher value
3. Save settings

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F8o1CvbgZhB7OzJUGoVSF%2Fcloud%20run%20timeout.png?alt=media\&token=f5736c8c-4d53-45b2-a2d6-7c64696de9ee)

Now BugBug will give your website more time in the cloud to load and operate.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/troubleshooting/cloud-tests-sometimes-failing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.