# Running Rules at Specific Time
**URL:** https://discuss.elastic.co/t/running-rules-at-specific-time/375659
**Category:** Kibana
**Tags:** elastic-stack-alerting
**Created:** [March 10, 2025, 3:22pm UTC](https://discuss.elastic.co/t/running-rules-at-specific-time/375659 "2025-03-10T15:22:46Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@erikg](https://discuss.elastic.co/u/erikg)
#### Post date: [March 10, 2025, 3:22pm UTC](https://discuss.elastic.co/t/running-rules-at-specific-time/375659/1 "2025-03-10T15:22:47Z")
Hello,
I am migrating some Watchers into Rules. I use cron schedule in Watcher to execute the alert at specific time, 6:30 am. The issue is I am not sure if this is possible in Kibana Rules? Or am I missing something?
---
### Author:  [@richcollier](https://discuss.elastic.co/u/richcollier)
#### Post date: [March 12, 2025, 4:15pm UTC](https://discuss.elastic.co/t/running-rules-at-specific-time/375659/2 "2025-03-12T16:15:06Z")
>
>
> For reference, Watcher allows some uber-flexible ways of scheduling, documented …as "triggers", documented here:
>
> https://www.elastic.co/guide/en/elasticsearch/reference/current/trigger-schedule.html
>
> I think I'd be happy with having our existing \`interval\` type scheduling and a \`cron\` one, and we can later add things like \`hourly\` if cron ends up being too obtuse for humans (it will).
>
> So, I think what should happen is we create a top-level \`schedule\` object that takes one of \`interval\` or \`cron\`, which should be fairly future-proof, as we can add more properties like \`hourly\` later.
>
> Note, this probably then also applies to Task Manager, as we attempt to move alerting's scheduling directly to task manager (seems like they are kinda independent right now).