Expand my Community achievements bar.

SOLVED

Stop workflows finished but that have an activity paused?

Avatar

Level 5

Some users pause activities inside the workflow. 

Since the status says "finished", I thought they have ended and that paused activity meant nothing. However, I've been told by Adobe Support that those workflows are consuming resources.

What would be an efficient way to stop all of them? How can I filter those workflows with an activity in pause state and stop them?

ogonzalesdiaz_0-1723234757781.png

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @ogonzalesdiaz ,

Go to xtk:workflow schema's data tab > Advance filter... > apply the below condition,

 

data contains mask="2"

AND

@state equals to Finished

ParthaSarathy_1-1723385047340.png

 

The above will list out all the workflows which are in finished state but has a activity in 'Enable but do not execute' mode.

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

Hi @ogonzalesdiaz ,

Go to xtk:workflow schema's data tab > Advance filter... > apply the below condition,

 

data contains mask="2"

AND

@state equals to Finished

ParthaSarathy_1-1723385047340.png

 

The above will list out all the workflows which are in finished state but has a activity in 'Enable but do not execute' mode.

Avatar

Level 5

Hi @ParthaSarathy , any documentation on what  mask="2" means? Maybe there is mask 1,3,4 etc.

Doing "Unconditional stop" doesn't change the paused activity to other state. There are more than 200 workflows with a paused activity. 

Is there any action I can do as a "Mass updated of selected lines" ???

Avatar

Community Advisor

@ogonzalesdiaz , Not sure about the documentation, but below are the values and its meaning,

mask="1" > Do not enable
mask="2" > Enable but do not execute
mask="0" > Normal Execution (Default)

And there is no option to remove 'Enable but do not execute' using 'Mass updated of selected lines', so have to manually modify it.

Hi @ogonzalesdiaz Unconditional stop would help with this scenario, it did work for us.