Hi,
I am facing a random issue. Restarting the element fix it for few days.
Below is the sequence of execution:
Timer 1 > Group 1 & Group 3
Group 1 > Session 4 > Param 506 > QAction 506
Group 1 > Session 1 > Param 211 > QAction 211
Group 3 > Session 3 > Param 346 > QAction 346
I have added exception handling & logging to all QActions.
After running for a few days/weeks (randomly), QAction 211 stops triggering for several days until we restart the element.
StreamSniffer has http call for all three Sessions even when QA211 stopped triggering.
We have log for QA506 and QA346 but no log for QA211.
Hi Muhammad,
QAction 211 will only be triggered if the value of parameter 211 changes, maybe that is not changing, while others are.
Hi Mihammad,
You can set up a trigger to clear the parameter (trigger "after" the group), which will eliminate the need for a checkTrigger in your QAction.
This approach ensures that, even if the code in the QAction doesn’t reach the end, the parameter will still be cleared automatically.
Hi Silva, Can you please share the details how to setup clear parameters trigger? Is this through QAction attribute from which we can call trigger once competed?
Hi Muhammad,
You have two options for clearing the parameter when working with trigger groups:
1) Before Group Trigger: Set a "before group" trigger to clear the parameter before sending the command to retrieve data. This ensures the parameter is reset in advance, avoiding any residual values.
2) After Group Trigger: Use an "after group" trigger to clear the parameter once all actions in the group have completed. If you have an QAction triggered by a parameter change, the "after group" trigger will clear the parameter only after the QAction and all related group actions have executed fully.
For further details on setting up an action to clear parameter data, check the documentation:
Thanks Jorge. I realized it later and now clearing parameter through trigger at the end of QAction so this can detect change.