Actions6
- Concurrency Gate Actions
- Dead Letter Queue Actions
- Retry Strategy Actions
Concurrency Gate → Release
AI-generatedSummary
Release an active concurrency lock for the specified gate key, using an explicit lock ID or one read from the incoming item. Add gate status metadata to each output item and send it through the Allowed output.
Inputs
- Gate Key (required) — Identifies the gate whose lock should be released; can be set per item with an expression, for example a customer ID.
- Lock ID — Explicit lock ID to release. Takes precedence over the value read from Lock ID Field.
- Lock ID Field — Dot path in the input JSON containing the lock ID; defaults to __concurrencyGate.lockId. Leave blank to use only the explicit Lock ID.
- Preserve Original Item — Defaults to true. Keeps the incoming JSON and binary data while adding metadata; when false, outputs metadata in a new JSON object.
Output shape
Two output branches: Allowed and Blocked. Successful operation results go to Allowed; Blocked is unused during normal release.
For each input item, removes the matching active lock for the gate key after expired locks are cleaned up. If no ID is provided or the ID is not active, it still outputs the item with __concurrencyGate metadata describing the reason and updated activeCount. Gate state is stored in workflow global static data. Errors with Continue On Fail enabled are sent to Blocked as error items.