Exclusive Gateway has outgoing sequence without condition

[sukhveer]

Hi,
So i have updated activiti 5.10 to 5.11. I was having an exclusive gateway with outgoing sequences and no condition on them. It was working fine with 5.10 but after updating i am getting following error.
org.activiti.engine.ActivitiException: Errors while parsing:
Exclusive Gateway 'exclusivegateway1' has outgoing sequence flow 'flow5' without condition which is not the default flow. | exclusivegateway1 | line 13 | column 5
Exclusive Gateway 'exclusivegateway1' has outgoing sequence flow 'no' without condition which is not the default flow. | exclusivegateway1 | line 13 | column 5

i can add condition for future workflow instances but i am looking for a fix for worlflows that are already in process.
Please don't ask why i didn't add conditions earlier.
P.S i tried 5.12 as well but same issue.

[jbarrez]

Unfortunately the fix is not a nice one here. The clue is to get your xml from the database, update it and write it back.

I got some code lying around that probably has the skeleton to do so. Would you be interested in this?

[sukhveer]

If you could send me skeleton code that will be great help.

[sukhveer]

just solved my issue…. its working

[jbarrez]

Awesome! How did you fix it?

[jackdd]

Hello,

we got the same error when update from version 5.8 to 5.13. Can you give us some suggestions how to fix this.

[bhaskar1]

Hi , ran into same issue after upgrading from 5.9 to 5.13.  Most of the API calls to Runtime service fails with  following error

Error Message : Errors while parsing:
Exclusive Gateway 'exclusivegateway5' has outgoing sequence flow 'publishSucceeded' which is the default flow but has a condition too. | exclusivegateway5 | line -1 | column -1
Exclusive Gateway 'exclusivegateway6' has outgoing sequence flow 'retryFailedExecution' which is the default flow but has a condition too. | exclusivegateway6 | line -1 | column -1

Any ideas?

[jbarrez]

yes - like I said above: you need to fetch the process from the database and update the xml.

[bhaskar1]

Thanks fixed this by migrating all inflight process instances and tasks to latest process definition(latest deployment) .  In our scenario, the definitions haven't changed , so I thought its probably alright to refer to new definition.

Could you please share  your skeleton code to do the XML update?

[krigu]

I would also gladly appreciate the skeleton code? Is it somewhere available?

Thanks
Krigu