When a batch recipe is running and a phase that is not yet active in this batch recipe is edited on the client in the phase edit dialog, the runtime on the server can close unexpectedly when the phase becomes active.
When a batch recipe is running and a phase that is not yet active in this batch recipe is edited on the client in the phase edit dialog, the runtime on the server can close unexpectedly when the phase becomes active.
An issue has been addressed where the runtime on the server closed unexpectedly when a phase became active that was currently open for editing on a client. Now the runtime on the server no longer closes. The user on the client receives the message on closing the phase edit dialog that the changes were not saved as the phase has become active.
available from 7.00 SP0 build 2