By default, optiSLang sets the working directory of custom integration nodes directly to the *.opd path. As a consequence, using two custom integration nodes within the same system level is not recommended as the latter one overwrites the data of the first one. While the custom integration node SignalMOP_SoS automatically enforces a distinct working directory, you should choose the Distinct working dir option in the Additional options dialog box of the other custom integration nodes. Another simple workaround is to place the custom integration node into a simple System node, which creates its own working directory.

You can find a custom integration node either by searching for the module name or at Process chain elements > Add-Ins.