When you publish an eSpace containing modified process flows, all of the executing process instances that were based on the former process flows are automatically upgraded by the OutSystems Platform. This topic lists some examples of the impact of removed activities on executing process instances.
In this case the process instance is executing the deleted activity: the execution is suspended.
The process instance has to be analyzed in Service Center to decide whether it can continue or should be stopped.
In this case, you avoid having a process instance suspended if you change the process in the following way:
This way, processes are not suspended because activities continue to exist in the process flow. All new processes will stop executing the deprecated branch. When there are not more active instances of activities to be deleted, those activities can effectively be deleted without suspending any process.
To check for active instances of activities, use one of the following (by order of importance):
Business Activity Monitoring (BAM): Use this reporting tool to check for active instances of activities. You can get it from the Forge;
Service Center: use this component to check for active instances of activities, however, is done manually, process by process;
Platform Database: query the Meta model of the Platform database for active instances of activities.
In this case the execution of the process instance has not passed the deleted activity and executes the new flow without it.
In this case the execution of the process instance has already passed the deleted activity and continues executing.
Overview of Upgrading Processes | Overview of Designing Processes