You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on deploying our workflow in the production environment , but we are facing a challenge here. We have Active/ Passive nodes and at a time we dont want to start both the nodes together. We are though using the concurrency here where it will execute the workflow one by one, but this is too time consuming. If we have 200 servers where 100 of them are primary and next 100 the secondaries, then according to our current policy it just executes the first workflow and put other 199 in delay queue.
Can we have some provision wherein we can set up some logic like {if...else... } statement depending upon the attributes that we can provide in the concurrency policy? For example if batch(considering batch to be one of our attributes) is Primary then execute 7 (or any number) of them parallely, but if batch is secondary then execute only 1 or no workflow at that time and vice a versa.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are working on deploying our workflow in the production environment , but we are facing a challenge here. We have Active/ Passive nodes and at a time we dont want to start both the nodes together. We are though using the concurrency here where it will execute the workflow one by one, but this is too time consuming. If we have 200 servers where 100 of them are primary and next 100 the secondaries, then according to our current policy it just executes the first workflow and put other 199 in delay queue.
Can we have some provision wherein we can set up some logic like {if...else... } statement depending upon the attributes that we can provide in the concurrency policy? For example if batch(considering batch to be one of our attributes) is Primary then execute 7 (or any number) of them parallely, but if batch is secondary then execute only 1 or no workflow at that time and vice a versa.
Beta Was this translation helpful? Give feedback.
All reactions