Hi Dojo,
How is possible that a virtual element goes to timeout? There are any ways to investigate the root cause of this behavior? Could it be a driver problem? Note that virtual element has some element connections configured. Could it be related to elements connected?
Daniel Martinez [DevOps Enabler] Selected answer as best 7th March 2023
Hi Daniel,
Could be that your virtual element is running a connector that is making use of call in a QAction (NotifyDataMiner 106) that raises a timeout alarm in a specific situation?
If the connector contains code like this, it could be the origin of the alarm.
Daniel Martinez [DevOps Enabler] Posted new comment 3rd March 2023
Hi Bruno,
I’ve checked the driver but it has no NotifyDataMiner call on it and has no code that you share. To update element state, in QActions parameters are passed as “inputParameters” and after its values are checked. Depending if a parameter is different to normal value, a “SetParameter” is done. So I understand that there’s no way to create a timeout state with this code.
Note that same parameters passed are the triggers.