Fix "Test did not see a new command for 90 seconds, timing out" in Sauce Labs. Here is the exact snippet you need for Test did not see a new command for 90 seconds, timing out in Sauce Labs, plus how it works, the common mistakes, and related references.
The code
likely_cause: Idle timeout: no command sent within the limit. fix: Increase idleTimeout in sauce:options or keep the session active.
How it works
Use this as part of your automated test flow. Wait for the element or state you are acting on to be ready rather than assuming it, and pair the call with an assertion so a failure is explicit rather than a silent pass. Small, focused snippets like this are easier to debug and reuse than long, tangled test steps.
When to use it
Reach for this when you need Test did not see a new command for 90 seconds, timing out in Sauce Labs. Keep your locators stable and your waits explicit, and confirm the snippet against your installed version — automation APIs shift between major releases, so the exact signature can change over time. When in doubt, check the official documentation for the current form.
Common mistakes
- Running the step before the page or element is ready
- Copying a snippet from a different major version of the tool
- Skipping the assertion, so a failure passes as green
- Hardcoding brittle locators that break on small UI changes
Related references
Applitools A Test Is Already Open Eyes Not Closed · Sauce Labs Unauthorized · Browserstack Session_not_created
Frequently asked questions
How do I handle Test did not see a new command for 90 seconds, timing out in Sauce Labs?
Use the snippet shown above, and wait for the relevant state before acting so the step is reliable.
Why isn't my snippet working?
Most often it is a timing or version issue — make sure the element is ready and that the snippet matches your installed version of Sauce Labs.
