OK, with the help of @momocampo, we now tested it out and it looks like:
You can only have ONE "hold" node with synchronize option enabled in your whole workflow.
As said, in 1.0 (and the betas) the problem is already sorted out.
I think to workaround your current problem, it should be easy for you to get rid of 2 unneccessary hold nodes (with sync option enabled) that are in your workflow before all the encodes are done. Replace them by either Hold nodest that are set to sleep(1) or by some populate variables or delete them completely
Status monitor - disabling for some workflows?
Re: Status monitor - disabling for some workflows?
emcodem, wrapping since 2009 you got the rhyme?
Re: Status monitor - disabling for some workflows?
Leaving only one "HOLD-sync" node solved this issue!emcodem wrote: ↑Tue Feb 11, 2020 12:15 pm OK, with the help of @momocampo, we now tested it out and it looks like:
You can only have ONE "hold" node with synchronize option enabled in your whole workflow.
As said, in 1.0 (and the betas) the problem is already sorted out.
I think to workaround your current problem, it should be easy for you to get rid of 2 unneccessary hold nodes (with sync option enabled) that are in your workflow before all the encodes are done. Replace them by either Hold nodest that are set to sleep(1) or by some populate variables or delete them completely
Thanks a lot for helping me out!
And ofcourse, looking forward to 1.0.0 release!
Re: Status monitor - disabling for some workflows?
Yeahhhhh, great!