If i look in the universal process flow monitor i can see that the flow is started as many times as i executed the task, so if i ran it 5 times i need to hit cancel 5 times and the process flow monitor shows the flow running 5 times.

Hi Guido,

It seems to me like two successor tasks are queued for every executed task. This could be the case when there are two green arrows.

Can you verify that there isn’t a second green arrow-to-self hidden in this process flow?

I can confirm that there weren’t 2 arrows, i remade it with just start - task - decision - stop. where the decision either loops back after execute and stops after cancel. But exact same result as before. This also works like expected/normal on windows gui, but not on universal.

This sounds like a bug, please submit a ticket and include a HAR file showing the http traffic when this issue occurs.

There is a new feature where you can repeat a task, but we have flows to repeat tasks (made before the repeat was added), and somehow 1 task had a repeat flow and the repeat after execute on, which causes a sort of loop. Either unticking or removing the flow fixed it.