You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I am looking for is something to do scheduled runs like:
Starting 12/24/2024 until 1/1/2025 do abc every 1 day 4 hours and 20 minutes.
From what I saw in the documentation, toad scheduler can do the 1 day 4 hours and 20 minutes nicely, but there isn't a way to have an offset for the start time or to set an end time.
For the usecase, if the start date is in the past then the next run needs to be calculated using the original start date and the interval to avoid excessive runs if there are application restarts, etc.
This feature can also enable the developer to build persistency across restarts by saving the jobs to a db and rescheduling them from the db to toad scheduler at every startup with minimal impact on the original run schedules.
The text was updated successfully, but these errors were encountered:
In my case what I'm looking for is say start of the day is say 7:15 min the morning and then every 10 min i.e. 7:25,7:35,7:45.... so on.
This will be helpful feature if the time interval is odd like every 7min or something with start time not the start of hour.
What I am looking for is something to do scheduled runs like:
Starting 12/24/2024 until 1/1/2025 do abc every 1 day 4 hours and 20 minutes.
From what I saw in the documentation, toad scheduler can do the 1 day 4 hours and 20 minutes nicely, but there isn't a way to have an offset for the start time or to set an end time.
For the usecase, if the start date is in the past then the next run needs to be calculated using the original start date and the interval to avoid excessive runs if there are application restarts, etc.
This feature can also enable the developer to build persistency across restarts by saving the jobs to a db and rescheduling them from the db to toad scheduler at every startup with minimal impact on the original run schedules.
The text was updated successfully, but these errors were encountered: