To the best of my knowledge there are 2 types of timer.
1) Default Timer which could be changed only during design time.
2) Effective timer which runs at runtime.
Question 1) Which of them has more precedence. By this I mean if One is said to "When publish" and another to "Regular interval" which will work?
Question 2) If both will work and a regular interval was set to after ever 20 min on effective side and on publish on default side. Ideally the natural schedule of timer is 0, 20, 40, 60 ... if the publish button is trigged on 24 then will the next timer run on 40 or now it will run as 44,64,84...?
Hello @Shlok Agrawal
I am assuming your question is related to the configuration on Service Studio (Default Timer Schedule) versus the configuration in Service Center (Effective Timer Schedule).
If you create a timer in Service Studio and define the schedule to be When Publish, as soon as you publish the module, the timer will be triggered.
After that, you go to Service Center and set the EFFECTIVE schedule to be every 30 min starting at 00:00.
From now on, your timer will run every 30 min starting from 00:00, as the EFFECTIVE schedule takes precedence over the default schedule (that will now be ignored).
BUT... (There is always a BUT)
In your module, the schedule is still defined as "When Published".
If you PUBLISH it again (the module), while the EFFECTIVE schedule will not be changed back (so your custom schedule will still work), the timer WILL run because of the publishing.
So, if your effective schedule is 00:00 10:00 22:00 and you publish the module at 9:45 (and in Service Studio it is set to run "When Publish", it will run at:
00:00 9:45 10:00 22:00 00:00 10:00 22:00 and so on.
So, no "prejudice" to the EFFECTIVE schedule (It will still work as expected), but you WILL have the timer running at the time of the publishing as well.
Hope this helps.
Cheers.
Heh, that's a good one Eduardo, didn't think of that situation. I should update my timer article now :). Thanks for pointing this out!
My pleasure.
I actually had to test to see what would happen :)
Thanks @Eduardo Jauch.
Got cleared.
Hi,
Below are answer of your question.
ANS : first execute the when publish and second Regular interval .
Ans: If you trigger button then manual then next time again automatic timer recalculate so it will run as 44,64,84 .
Hi Shlok,
Your knowledge is unfortunately wrong. There's only a single type of timer, which has a single schedule that determines when it will run. I have written a lengthy article that goes into the gritty details, but there's no real distinction between "When published" and another schedule. So as for your questions:
1) There's a maximum number of timers that are allowed to run at any one time, and if that maximum is reached, no other timers will run. If there's less than that maximum, the timer(s) with the highest priority are allowed to run, regardless of whether the schedule is "When published" or another schedule, or whether the timer is scheduled manually.
2) The default schedule is the schedule that is set (i.e. made the effective schedule) when the timer is first published/created. The effective schedule is the only schedule that the Platform looks at. But please read my article if you want to understand the actual scheduling better.
Just something funny I found.
Even if you have an EFFECTIVE schedule in place, if your timer is configured, in Service Studio (Default schedule) to run "When Publish", it will run after the publishing, because of the publishing.
(And that is not what I would expect to happen)
Well, since the "When Published" is triggered like a manual run by the Deployment Controller as opposed to by the Scheduler, I'm not at all surprised. Just something I never thought of.
Thanks @Kilian Hekhuis
Your article helped a lot and I got a lot to know regarding timers.