topic RE: Scheduler 'Run Now' doesn't work as intended in Product Forum

Scheduler 'Run Now' doesn't work as intended

splittergal — Mon, 17 Feb 2020 15:05:00 GMT

Hi Blue Prism,

We are working as a multi national team(Denmark + Vilnius), when Vilnius developers press 'Run Now' on a schedule it's starting to run after 1 hour delay. It's the exact same time difference between our countries, so I expect that 'Run Now' is using some sort of local time when writing to the database. The server is located in Denmark, so makes sense we don't see it when we manually run the robots from Denmark.

Best regards
Frank Jelstrup

------------------------------
Frank Jelstrup
------------------------------

RE: Scheduler 'Run Now' doesn't work as intended

david.l.morris — Mon, 17 Feb 2020 15:15:00 GMT

Correct, when you click Run Now, it inserts the local time as an entry as a scheduled run and then BP periodically checks the DB for whether it should run anything based on the application server's time zone or if it's missed any runs. It's annoying, but the best way I've seen to handle the issue is to either have them remote into a machine that is on the correct time zone or change their local system time zone to match that of the application server.

This would probably be a good thing for Blue Prism to include in a future update. I suspect it's already on their list because this is a known issue.

------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------

RE: Scheduler 'Run Now' doesn't work as intended

HakanEngman — Tue, 18 Feb 2020 11:57:00 GMT

Well, the opposite is even worse. We have server in EET timezone and runtime resources in CET, then nothing happens as the start is considered to be in the past…

------------------------------
Hakan Engman
Automation engineer
Teliacompany.com
Europe/Stockholm
------------------------------

RE: Scheduler 'Run Now' doesn't work as intended

david.l.morris — Tue, 18 Feb 2020 13:42:00 GMT

@Hakan Engman That sucks. =( This suggestion may not be ideal, but one workaround (assuming only 1 hour difference like that) is to change the System tab > System group > Scheduler > 'Execute missed schedules from the past n minutes' setting to something like 65 minutes. This should result in Run Now working for you because it would be recognized as a missed schedule from one hour in the past. Again, not perfect and it sounds weird but it should work.

------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------

RE: Scheduler 'Run Now' doesn't work as intended

HakanEngman — Tue, 18 Feb 2020 13:48:00 GMT

Well, another way of doing it is to temporary switch the clock in the session where you run the UI. Then it works as expected. (or use the AutomateC.exe file.)

------------------------------
Hakan Engman
Automation engineer
Teliacompany.com
Europe/Stockholm
------------------------------

RE: Scheduler 'Run Now' doesn't work as intended

splittergal — Tue, 18 Feb 2020 14:03:00 GMT

Thanks for your suggestions guys 🙂 But it do seem like it's mainly "hacks" you are proposing. I know that AutomateC.exe can start a schedule, but not sure if got any possibility of changing the starttime to +1 or -1 hour from now. Could be looked into.

------------------------------
Frank Jelstrup
------------------------------

RE: Scheduler 'Run Now' doesn't work as intended

vivek.kumar.goel — Wed, 19 Feb 2020 03:41:00 GMT

Please search for the idea in ideas forum, if not present, please do propose it there.

------------------------------
Vivek Goel
"If you like this post, please press the "Recommend" Button.
------------------------------