Scheduling bugs
Scheduling bugs
Hi Martin,
there are 2 bugs related to scheduling:
1.) when actions get delayed, the order in which they start running is determined by the time of creation, not the scheduled time. Let say you have two actions:
Action1 - date created = 20.09.2017 14:00, scheduled time = 21.09.2017 10:00
Action2 - date created = 20.09.2017 13:00, scheduled time = 21.09.2017 11:00
Now when you start the processor 21.09.2017 at 12:00, the Action2 start running first, even when it is scheduled to the later time. This is really confusing and annoying sometimes and get the timing of the actions messy.
2.) rescheduling of the action doesn't have effect on the start of the action, when you reschedule the action after it's delayed. Example:
Current time is 21.09.2017 13:00
SharedAction1 is currently running
SharedAction2 is scheduled to 21.09.2017 12:00 and is waiting (because option "Process Single account at time" is turned on)
Now when you reschedule the SharedAction2 to 22.09.2017 13:00, it starts immediately after SharedAction2 is completed, ignoring it's scheduled time.
Please have a look Thanks.
there are 2 bugs related to scheduling:
1.) when actions get delayed, the order in which they start running is determined by the time of creation, not the scheduled time. Let say you have two actions:
Action1 - date created = 20.09.2017 14:00, scheduled time = 21.09.2017 10:00
Action2 - date created = 20.09.2017 13:00, scheduled time = 21.09.2017 11:00
Now when you start the processor 21.09.2017 at 12:00, the Action2 start running first, even when it is scheduled to the later time. This is really confusing and annoying sometimes and get the timing of the actions messy.
2.) rescheduling of the action doesn't have effect on the start of the action, when you reschedule the action after it's delayed. Example:
Current time is 21.09.2017 13:00
SharedAction1 is currently running
SharedAction2 is scheduled to 21.09.2017 12:00 and is waiting (because option "Process Single account at time" is turned on)
Now when you reschedule the SharedAction2 to 22.09.2017 13:00, it starts immediately after SharedAction2 is completed, ignoring it's scheduled time.
Please have a look Thanks.
- martin@rootjazz
- Site Admin
- Posts: 34627
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Scheduling bugs
checking
- martin@rootjazz
- Site Admin
- Posts: 34627
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Scheduling bugs
Confirmed (2) and fix coming
(1) is going to be tricky. When the app restarts AFTER the schedule date for both, when it comes to the scheduler they no longer have the date, so they are started in creation order.
(1) is going to be tricky. When the app restarts AFTER the schedule date for both, when it comes to the scheduler they no longer have the date, so they are started in creation order.
- martin@rootjazz
- Site Admin
- Posts: 34627
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Scheduling bugs
(2) The next update will fix this. I shall let you know when it is ready.
Regards,
Martin
Regards,
Martin
- martin@rootjazz
- Site Admin
- Posts: 34627
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Scheduling bugs
You don't have to restart the app, it is enough to have the action be delayed because of the other actions running. So let's say you use 2 threads in processor and you have 2 actions running. The other two actions are waiting, because there's no free thread. When one of the action complete, the action with older date of creation will start running, even when it is scheduled to start later.martin@rootjazz wrote: ↑Thu Sep 21, 2017 7:33 pm (1) is going to be tricky. When the app restarts AFTER the schedule date for both, when it comes to the scheduler they no longer have the date, so they are started in creation order.
- martin@rootjazz
- Site Admin
- Posts: 34627
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Scheduling bugs
Is the same thing. As soon as the scheduled date passes the action is "available" for processing. When a thread becomes free, all actions that are "available" are checked. Oldest creation date is then processed.jrichards wrote: ↑Fri Sep 22, 2017 8:58 amYou don't have to restart the app, it is enough to have the action be delayed because of the other actions running. So let's say you use 2 threads in processor and you have 2 actions running. The other two actions are waiting, because there's no free thread. When one of the action complete, the action with older date of creation will start running, even when it is scheduled to start later.martin@rootjazz wrote: ↑Thu Sep 21, 2017 7:33 pm (1) is going to be tricky. When the app restarts AFTER the schedule date for both, when it comes to the scheduler they no longer have the date, so they are started in creation order.
Re: Scheduling bugs
So it's not possible to change it and keep the scheduled time accounted?
Re: Scheduling bugs
BTW after the fix of (2), the shared actions start running simutaneously, even when the "Process single account" is set on. Could you fix that?
- martin@rootjazz
- Site Admin
- Posts: 34627
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact: