...
You have 2 devices in your sig.
I have had intermittent problems where a timer is sent to the wrong device.
...
Yes, I do have two devices, but the timer that was sent but left in "scheduled" state on the server was sent to the right box, and the timer with the error was sent to neither.
Yes, as with you, I get the occasional timer after being set in the correct box, I still see it is still left in the scheduled state. It remains like that every day after being set.
As with the timer with the error indication, I have had it posed to me, by Ice tech, one of the boxes, calls for updates, somehow selects the wrong box in the Ice server, and sends a new timer there.
The reasoning that was given was that it will be the second box in your device list in the Ice server that calls for the update, and selects the first in the list.
I've seen a couple of results from this. The first result is that I see a timer being set in the wrong box.
The other result is that the timer being sent to the wrong box finds that there is a conflict as you already have 2 timers set for that time, and ends up being flagged as an error.
As an aside to this, even though we set up device names in the Ice server to match our box names, the request that is sent is by ID, in the case of 2 devices in the list, either 0 or 1, not the box name.
So without seeing a trace for this, the 2 different causes for this may be, second box, ID = 1, somehow sends a request for ID = 0.
Or sends a request for ID = 1, and the Ice server selects ID = 0.
I've also talked with BW people about this, the tech said that he'd like to set this up on their boxes, and trace it.
But I suspect that the occurrence is too intermittent to be able to be caught, without monitoring virtually 24/7.