Flow designer

[dhruvajmera]

(XANADU Patch 😎 In flow designer, after modifying an existing working flow, it is saving but not activating, it gives the error:
INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified
There is no custom actions or scripts used, only OOB actions like asking for approval, updating record and sub-flow etc.
And after removing the change to make it as before, it still giving the same error and not activating.
I checked almost everything, it is for this flow only, activating on test instance without any error, tried clearing cache.

[dhruvajmera]

I created this flow a month back and it is quite big so redoing every step is not feasible.
I need some modifications in it, when I am trying to add or remove even a stage it is showing this invalid xml error.
making the flow again as before by undoing any change still giving the same error.
Activating and modifying on test instance without any error.

[Mark Manders]

You are still not showing us what you did, so we can't tell you what it is that is throwing the error. 

I am also not saying you need to recreate the flow, but to go back to the version that worked and update the changes you made one by one until you run into the issue again, so you know which update causes it. 

Are there any version differences between the instances? 

[Ankur Bawiskar]

@dhruvajmera 

So since you said it was created earlier and you are now trying to add something to it.

Please check the steps which you are adding are added with correct details such as you are using correct flow variable etc.

are you calling any subflow etc and is that published?

you will have to debug from your side as it's big and try to see what recent changes you did

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Greg D]

We are getting the same error as well with Xanadu patch 7. Flows that would previously activate are now throwing the error without rhyme or reason. It's almost like the xml validation in core changed somehow with the latest release. I'm going to submit a ticket to HI. Any luck on your end?

[Greg D · Accepted solution]

There is a Problem record for this but its not published yet so SN knows there is an issue. A work around is to copy the flow which is not ideal. Just from what I gather it is an issue with the v1 to v2 conversion. Hopefully they publish it with a fix soon.