There looks to be a bug when you would have multiple local monitors selected and attempt to schedule their checks via the “random” interval option. Instead of being granted the freedom to set any value to this field as would be the case when you would select the monitors individually (at least with my Professional account) Distill acts as if the selected monitors would be cloud monitors and forces the minimum value to 300s, also including the following message: “Use local monitor for smaller interval or Upgrade Account”
@shadowmoses Thanks for the detailed report — this is a good observation.
What you’re running into is a known limitation of the Cloud Monitor dashboard, not a bug with local monitors themselves.
When you select multiple monitors from the Cloud Monitor dashboard and try to batch-edit the schedule, Distill applies cloud-monitor constraints to the edit. That’s why you’re seeing:
-
A minimum interval of 300 seconds, and
-
The message: “Use local monitor for smaller interval or Upgrade Account”
Even though the monitors are local, batch edits made from the Cloud dashboard are validated using cloud rules.
How to work around this
If you use the Local Monitor dashboard instead, you can batch-edit multiple local monitors and:
-
Set the random interval with a minimum as low as 5 seconds
-
Avoid the 300-second cloud restriction
We agree this can be confusing, and we appreciate you calling it out. Your feedback helps us identify areas where the UI behavior could be clearer or improved.
Thanks for the clarification!
1 Like