Hi,
I was wondering if anyone else experienced the case, that two deployments get triggered at the same time from the same plan? They both have the same name and are only 1s apart (if the timestamp differs at all)
Normally it shouldn't even be possible, as the name of the deployment has to be unique, but my guess is, that the events get triggered so fast, that the check if the name is already in use, doesn't work.
This is nothing that happens really often, maybe 5 out of 3000, but it does happen.
So yeah, does anyone has an idea what might cause something like that? my current theory is only, that something with the hardware is wrong, that e.g. the mouse button triggers twice or something like that.
Also I'm curious to know, why there isn't a blocking mechanism build-in that only allows one "save" event at all
thanks.
michael
we're currently running 5.5.2.191