Skip to content
NEWMarketplace and the trig8n Agent: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Building Blocks & Utilities

Building Blocks & Utilities

Prevent Concurrent Workflow Runs with Redis Locks

When called by another workflow, it uses a Redis key to mark a run as started or finished so duplicate parallel executions can be blocked.

Import it free Sign in to open it

What it does

## Set workflow start Inputs: - action -> "set" - key -> a string used for tracking - value -> "working" by default but you can use whatever, you can use this multiple times in combination with get to track progress of a execution. * Remove unused inputs when calling workflow *

The steps

  1. When Executed by Another Workflow
  2. Switch
  3. When clicking ‘Test workflow’
  4. If2
  5. Is Workflow Active
  6. Set Workflow Active
  7. Set Workflow Finished
  8. Get Key
  9. Set Key
  10. UnSet Key
  11. Set Timeout
  12. set continue
  13. If
  14. Is Workflow Active1

31 steps in total.

Similar automations

Building Blocks & UtilitiesPrevent Concurrent Workflow Runs Using Redis32 stepsBuilding Blocks & UtilitiesPrevent Duplicate Webhook Runs with a Redis Lock24 stepsBuilding Blocks & UtilitiesPrevent Concurrent Runs with Redis Locking14 stepsBuilding Blocks & UtilitiesPrevent Overlapping Scheduled Runs with a Redis Lock10 steps