Hello,

I am running into a race condition when triggering multiple simultaneous automations from SRM booking manager custom events.

When a booking event fires it launches a script which then triggers a subscript that should lockout the dummies defined in the subscript. See below:

var subscript = engine.PrepareSubScript("MakeSplice");
subscript.SelectDummy("Source", source);
subscript.SelectDummy("Destination", destination);
subscript.LockElements = true;
subscript.WaitWhenLocked = true;
subscript.Synchronous = true;
subscript.StartScript();

If I trigger the multiple scripts manually I can see the first subscript locks the element, and the following subscripts wait for the first to unlock before proceeding, as I would expect. However, when the booking manager triggers the same scripts they do not queue properly. Although the first script to fire locks the element, it does not prevent competing scripts from making changes on the same element.

Is this expected behaviour or a bug? Is there some other way I can enforce the element lock when triggering scripts from the booking manager?