What happens to the deployed process version regarding changes in the Build tab?

The deployed process version remains isolated from any changes made in the Build tab. This means that any modifications or updates made in the Build tab do not affect the processes that have already been deployed. When a process is deployed, it represents a specific version that is actively being used in production or in practical scenarios.

This isolation allows developers the flexibility to update and enhance the design and functionalities of their processes without disrupting existing deployments. Users can continue to run the deployed version while still improving and testing new versions in the Build tab. When changes are deemed appropriate for production use, a new version can then be deployed, thus replacing the existing, isolated version with an updated iteration.

In contrast, automated updates or locking mechanisms do not apply to deployed processes, as these would potentially disrupt existing workflows and create inconsistencies for users who depend on the deployed version for operations.