Hi Dojo,
An issue sometimes occurs in a driver where groups from timer 2 execute before groups from timer 1. Groups 1, 2 and 3 are of the type poll and group 15 is of the type poll action. As the timer 1 groups are for authentication purposes, when this happens the timer 2 groups are only executed 1h after the element starts leaving the corresponding parameters and tables empty for that time being.
So to fix this issue is there a way to configure the timer startup order?
In the timer settings, I notice a random option that delays the start of the timer. Do you think this is the best solution or is there an alternative?
Hi Samuel,
The initial attribute of the Time tag could indeed be a good approach for your use case, however, on the linked docs page you will notice a NOTE that states that this value is disregarded if the element card is opened.
Since if nothing is specified, all timers are started simultaneously, and since they behave as separate threads, there is no guarantee of order between their content.
Another option could be to use a condition on the other timers that they should only run when the condition is met and you could set it to wait for the token to be valid.
You could then have the initial attribute set to false and combine this with actions of type start timer to only activate the timer when the token is ready.
Please do note that this should be done with caution (read Starting/stopping timers | DataMiner Docs)