Skip to content

[Synthetics] Add note on timeout limits #3962

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+5 −0
Open

[Synthetics] Add note on timeout limits #3962

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
818fa01
[Synthetics] Add timeout limits
mdbirnstiehl Nov 17, 2025
cec3208
update wording
mdbirnstiehl Nov 17, 2025
cbecb3f
Merge branch 'main' into synth-timeout
mdbirnstiehl Nov 19, 2025
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
5 changes: 5 additions & 0 deletions solutions/observability/synthetics/configure-projects.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,6 +171,11 @@ Playwright has two types of timeouts that are used in Elastic Synthetics: [actio

Elastic Synthetics uses a default action and navigation timeout of 50 seconds. You can override this default using [`actionTimeout`](https://playwright.dev/docs/api/class-testoptions#test-options-action-timeout) and [`navigationTimeout`](https://playwright.dev/docs/api/class-testoptions#test-options-navigation-timeout) in `playwrightOptions`.

:::{note}
Browser-based journeys have a timeout limit of 15 minutes.
When `retry` is enabled (enabled by default), the journey attempts a second run if the first run times out. This allows for a maximum total runtime of 30 minutes: 15 minutes for the first run and up to 15 minutes for the retry.
:::

### Timezones and locales [synthetics-configuration-playwright-options-timezones]

The Elastic global managed testing infrastructure does not currently set the timezone. For {{private-location}}s, the monitors will use the timezone of the host machine running the {{agent}}. This is not always desirable if you want to test how a web application behaves across different timezones. To specify what timezone to use when the monitor runs, you can use `playwrightOptions` on a per monitor or global basis.
Expand Down
Loading