You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have two instances of the same business rule. The siddhi-app of one instance contains the following fragment
define trigger AfterDeleteNoiseAlarmsStatusTablesb25ux5y52uzs9nebsurf6r at '0 01 23 * * ?';
from AfterDeleteNoiseAlarmsStatusTablesb25ux5y52uzs9nebsurf6r full outer join NoiseAlarmsStatusTable#window.cron('* * * * * ?')
insert into LogNoiseAlarmsStatusAfter;
When we deploy two or several instances of the business rule, only the last deployed instance is the one working fine, the rest of the instances are stuck. However, once the last deployed instance is undeployed, the previous instance continues the workflow and executes the pending events.
It seems that both instances are sharing the same cron but only one is executed.
We also tested the same business rule in stream processor v 4.3 and it is working fine.
The text was updated successfully, but these errors were encountered:
We have two instances of the same business rule. The siddhi-app of one instance contains the following fragment
define trigger AfterDeleteNoiseAlarmsStatusTablesb25ux5y52uzs9nebsurf6r at '0 01 23 * * ?';
from AfterDeleteNoiseAlarmsStatusTablesb25ux5y52uzs9nebsurf6r full outer join NoiseAlarmsStatusTable#window.cron('* * * * * ?')
insert into LogNoiseAlarmsStatusAfter;
When we deploy two or several instances of the business rule, only the last deployed instance is the one working fine, the rest of the instances are stuck. However, once the last deployed instance is undeployed, the previous instance continues the workflow and executes the pending events.
It seems that both instances are sharing the same cron but only one is executed.
We also tested the same business rule in stream processor v 4.3 and it is working fine.
The text was updated successfully, but these errors were encountered: