For example, if you obtain a write-intent lock on a workflow before the Integration Service starts the workflow, the Integration Service runs the version of the workflow existing in the repository when the workflow starts. If you save changes to the repository before the workflow starts, the Integration Service runs the newly-edited workflow. If you save changes after the workflow starts, the Integration Service runs the original workflow and the repository updates the changes after the workflow completes.

When the workflow starts, the Integration Service obtains an execute lock on the workflow and tasks in the workflow. If you try to start the workflow, the repository displays a message stating that the workflow is already running. If you try to edit the workflow or task when another user has a write-intent lock, you receive an in-use lock.