# Why can't I run synthetics (beta) more frequently than every 3 minutes?
**URL:** https://discuss.elastic.co/t/why-cant-i-run-synthetics-beta-more-frequently-than-every-3-minutes/332324
**Category:** Elastic Observability
**Created:** [May 2, 2023, 3:56pm UTC](https://discuss.elastic.co/t/why-cant-i-run-synthetics-beta-more-frequently-than-every-3-minutes/332324 "2023-05-02T15:56:50Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jerrac](https://discuss.elastic.co/u/jerrac)
#### Post date: [May 2, 2023, 3:56pm UTC](https://discuss.elastic.co/t/why-cant-i-run-synthetics-beta-more-frequently-than-every-3-minutes/332324/1 "2023-05-02T15:56:50Z")
I'm specifically trying to check if my attempts to implement high availability for several Drupal and Symfony apps are working.
Using Uptime I was able to check as often as I wanted as long as I was willing to accept the storage and resource cost. That let me run the check often enough that I'd find out if users were effected when a part of my HA stack went down.
So, say, one Drupal container went down. I need to know if people will end up hitting errors between the time it goes down, and the time Traefik stops routing traffic to it.
So I was running Uptime every minute. The idea being that if a user hits the bad container, they won't really care that they had errors when the errors go away after a minute or less.
3 minutes, though... If I hit errors for more than a minute when visiting a site or app, I'm gone. Vamoosed.
Which is why I'm asking. Why can't I set the frequency to less than 3 minutes?
Or can I, and I just haven't found the option?
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 3, 2023, 7:11am UTC](https://discuss.elastic.co/t/why-cant-i-run-synthetics-beta-more-frequently-than-every-3-minutes/332324/2 "2023-05-03T07:11:11Z")
Hello @jerrac ,
Apologies for bit of uncertainty there. we have restored the option of every 1 minute in 8.8.0.
So for now you will have to wait for that release to go out.
>
>
> \## Summary
>
> Relates to https://github.com/elastic/kibana/issues/142655
> Resolv…es https://github.com/elastic/kibana/issues/142653
>
> Release notes
> \--
>
> All monitor schedules in Uptime Monitor Management/Synthetics app apart from the \[supported schedules\](https://github.com/elastic/kibana/pull/154010/files#diff-6e5ef49468e646b5569e213b03876de143291ca3870a7092974793837f1ddc61R33) have been deprecated.
>
> The only allowed schedules are the below:
>
> \
>
> Any monitor create in Uptime Monitor Management or Synthetics app using a schedule outside of the defined schedules in the screenshot have been moved to the nearest supported schedule.
>
> Description
> \--
>
> Adds a migration to transform unsupported schedules from Uptime Monitor Management to supported Synthetics app schedules. Also adds validation when an invalid schedule is used.
>
> Also removes zip url fields from monitors. These fields were originally included in the saved object spec anticipating a future zip url feature. That feature has now been replaced by project monitors, removing the need for zip url fields.
>
> \## Testing
>
> ⚠️ Note ⚠️
> \--
>
> It's suggested that you use a fresh instance of ES to test this PR. This can either be done by creating a brand new oblt cluster via oblt-cli, or by running \`yarn es snapshot\`. If you run this PR on an existing oblt-cluster, then switch back to main on that same cluster before this PR is broken, you'll break the cluster.
>
> Instructions
> \--
> 1. Check out 8.7.0
> 2. Create Uptime monitors with invalid schedules. Ideally, create one of each monitor type. Some example invalid schedules are 4, 8, 11, and 16, for example.
> 3. Create at least one of each type of project monitor by pushing monitors via the synthetics agent
> 4. Check out this branch
> 5. Navigate to Synthetics or Uptime once Kibana is done loading. Observe that each one of the invalid schedules was transformed into a supported schedule.
> 6. (Testing that decryption is still working after migration). Navigate to each one of the UI monitors' edit pages. Click save to resave each monitor. Then, visit the edit page again. If you don't see any page level errors, decryption is still working successfully
> 7. (Testing that decryption is still working after migration for project monitors). Change the global schedule your project monitors and repush. Check the global schedule of your project monitors one more time and repush again. If both pushes are successful, decryption is still working after the migration.
In future we are hoping to allow lower schedules as well at least for non-browser monitors.
Regards
---
### Author:  [@jerrac](https://discuss.elastic.co/u/jerrac)
#### Post date: [May 5, 2023, 4:22pm UTC](https://discuss.elastic.co/t/why-cant-i-run-synthetics-beta-more-frequently-than-every-3-minutes/332324/3 "2023-05-05T16:22:42Z")
Oh. Good. 🙂 Thanks!