Skip to main content
Committed ⭐️⭐️⭐️
December 10, 2025
Implemented

Enforce a max on concurrent workflows

Related products:Data Workflows
  • December 10, 2025
  • 4 replies
  • 73 views

In Data workflows I have a case where i would like a workflow to run every minute, but in certain cases the runs are longer than one minute. In this case, to maintain consistency in runs I do not want concurrent runs. In this case it would be helpful with an option to enforce non-concurrency in data workflows, as in if a data workflow already runs, when the trigger is set to run, the run is skipped.

4 replies

Practitioner ⭐️⭐️⭐️
December 10, 2025

Hi Adrian,

This is a great suggestion and the good news is that we are actually working on such a feature!

It will be made generally available in the API with the Q1 release.

Vincent

Jørgen Lund
Expert ⭐️⭐️⭐️⭐️
Product Manager
March 10, 2026

@AdrianLangseth This is now available, see API docs and in the user interface:

 

Committed ⭐️⭐️⭐️
April 13, 2026

@AdrianLangseth This is now available, see API docs and in the user interface:

 

How and where should one specify this in YAML Workflow definition, when deploying with toolkit?  

Committed ⭐️⭐️⭐️
April 13, 2026

@AdrianLangseth This is now available, see API docs and in the user interface:

 

How and where should one specify this in YAML Workflow definition, when deploying with toolkit?  

nvm, found it. For anyone else wondering, it is in the overarching workflow definition as a maxConcurrentExecutions.