Idea Details

Schedule change of hourly run calculation

Last activity 15 days ago
Walter Koller's profile image
By: Walter Koller
10-19-2021 10:38

The current way on how hourly runs are calculated is misleading and and limits functionality.

There are two date/time definitions in a Schedule:
Schedule:
Runs (eg HourlyMinutely)
Start on (eg 19.10.2021) 
Run At (eg 10:00)
Run hourly / minutely
Every (eg 5 hours)
between (eg 06:00 and 16:00

Expected behavior of the schedule would be to have following time table:
19.10., 11:00
19.10., 16:00
20.10., 06:00
20.10., 11:00
20.10., 16:00
.. to run at the same hours in the specified window.

The actual runs are scheduled for:
19.10., 11:00
19.10., 16:00
20.10., 07:00
20.10., 12:00
21.10., 08:00
The calculation is based on the initial Run At time and the hours are simply added regardless of day ends. (Since 5h frequency put in a calendar day is 24h +1h, there is a 1h shift in execution each day).
This is not only very confusing but also limits the hourly runs to values that can divide 24 with no remainder.

Please change the calculation to be based on the start value of the time window in the hourly parameter definition.
Or change the calculation to be always based at the Run At time each day. (so no continues calculation but resets for each calendar day)


Ideas Portal

If you like this idea – vote! Ideas with over 20 votes will be highlighted to our Product review teams.
• Discussion is healthy! If you have a question or comment, don’t be afraid to jump in and start a discussion in the comments section below.
• Community collaboration is key!
New
This idea is new to the community and hasn’t been reviewed yet. While in the New stage, an idea is open for voting and comments to further the discussion around this idea.
Duplicate
This idea already exists! A change to the Duplicate status will always include a comment linking to the existing idea, so all voting and feedback can be collected in one place.
Need More Info
We’ve reviewed this idea, and determined we need a bit more info before deciding on how to move forward. An update to the Need More Info status will always be accompanied by a comment explaining which additional details are needed. Ideas are still open for voting and comments while in the Need More Info stage.
Under Consideration
We have all the info we need and are currently considering the feasibility of implementing this idea. Ideas in the Under Consideration status are still open to community voting and discussion.
Not Planned
We’ve reviewed this idea, and determined that it’s not feasible to implement right now. Ideas in the Not Planned status are no longer open for voting.
Coming Soon!
We’ve reviewed this idea and have determined that it will be delivered in the near future. Ideas in the Coming Soon! status are not attached to a binding timeline, but there is a concrete plan to implement this idea. Therefore we will have status does not allow for voting.
Delivered
Congrats! Your idea has been accepted by the team and is now in production! Give yourself a pat on the back – you contributed to the improvement of one of Blue Prism’s products or services!