---
schema_version: "1"
id: 2b6b3463aabd501fc8caf5043231032bbd3572ba24d680046a4540da1be6866b
title: Lock Section
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/rpa-builder/latest/toolbox-flow-control-lock-section.md
canonical_url: https://docs.mulesoft.com/rpa-builder/latest/toolbox-flow-control-lock-section
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7ba38c4fc4d023485efb864c9cb07c22fbfb61542c318ffda5ff18c9d2cd23c2
description: MuleSoft Documentation Site
release: "6.7"
latest: true
---
---
product: RPA Builder
version: 6.7
is-latest-version: true
---

# Lock Section

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The _Lock Section_ action step is used to synchronize access if multiple parallel _Workflows_ need
to access a file or a mailbox, for example in the case of Robotic Applications. Synchronization is
achieved by preventing other _Workflows_ from accessing the file when it is in use.

A typical scenario where a _Lock Section_ might be used when a _Workflow_ is run in parallel in
different sessions. In this case, a _Robot Secure_ is used that enables parallel secure sessions to
be launched. If parallel secure sessions, such as in the example above, are running on virtual
machines on a server, then a file can be locked in synchronization on this server in order to allow
certain content to be read out alternately.

## Properties

**Misc**

- **Lock Token** Enter an individual token here. Individual tokens are typically only necessary if
  you work with virtual machines with identical installations running in parallel. Normally it is
  adequate to use the WorkflowGUID as the token.

- **WorkflowGUID** This field shows the GUID (Globally Unique Identifier) of the present _Workflow_.
  This GUID is intended to be unique anywhere in the world. However, for parallel, identical
  installations that use _Robot Secure_ and individual _Secure Sessions_, there is no guarantee that
  this ID will be unique.

Other Properties that are the same in all action steps are described in the section on **Common
Properties**. For reasons of clarity they are not shown here.

## Wizard

- **Lock on Workflow GUID** Enable this option if parallel executions of the same Workflow need to
  be synchronized across various _Secure Sessions_ when using _Robot Secure_. The GUID shown in the
  **Lock Token** field for the active Workflow makes use of this option.

- **Lock on user defined token** Enable this option if parallel executions of the same Workflow need
  to be synchronized in various _Secure Sessions_ using the _Robot Secure_. This is the case for
  virtual machines and parallel identical installations, for example. This option uses the token
  entered in the **Lock Token** field.

- **Lock Token** Enter an individual token here. All alphanumeric characters except \\ and / are
  allowed.