[zeiscas]

Hi,
I saw an old topic in this forum with this error and it seems it was a bug already fixed in version 3.1.3. I have the workflow on the following image where I want to loop always based on a condition. The sub-process is asyncronous. In some cases the flow must go to the sub-process and loopback to the task simultaneously, but in these cases I always got the error on title.
Am I doing something wrong?

Thanks.

[andreaadamczyk]

Hello,

Could you please tell me what are the conditions you are using in the inclusive gateway?

Thank you.

Regards.

[zeiscas]

Hello Andrea,

Basically, I have 2 boolean variables updated on a trigger (before assignment). When both are true, I want the flow to go both to the subprocess and back to the task. On the assignment window, I only have the next task for the Subprocess and not for the feedback task. Continuing the case, gives that error!
I tried several options, but without success.
As I needed to continue, I change it to a XOR. But with this solution the user needs to open the case once more than I wanted, just to confirm that all services have been processed, which is unecessary.

Thanks.

[amosbatto]

The problem is that ProcessMaker throws this error when going from a subprocess to an end event.
See:
viewtopic.php?f=41&t=731007&p=816163&hi ... ss#p816183

I filed a bug report about this, but I doubt that it will get fixed before version 4. For now, you will have to add an extra task between your subprocess and your end event to work around this problem.

[zeiscas]

Thank you, Amos.
As I wrote before, I already have a workaround. Not ideal, but it works.