Hello,
we are noticing a behavior that we consider weird: on all at chrontimer inside action is not working as expected, it since that action is ending before the next chrontimer, is it a normal behavior? and what is the solution? where should we put those chrontimers if not under an action?
snipet from EPL code:
action onload() {
spawn start() to context(“counting”);
}
action start() {
on all at(5, 2, *, *, *) {
RESET_COUNTS_STARTUP();
}
Hi,
I think there might be a misunderstanding on how listeners work. Yes, as you correctly observed, the start action finishes before the timer fires the next time. This is expected as the action only creates the listener which then live independently from the action. So even though the start action terminated, the listener will now fire every day at 02:05 until you terminate it.
I suggest you also study the explanation on monitor and listener leaks to ensure that you are not creating listeners without provision to terminate them at some point:
Best regards,
Harald