Currently converting a classic customization to a Kinetic WebUX in 2025.1.12.
I have this event that I added a kinetic-message-handler (KMH) after the false condition is met for troubleshooting the event. Now that I have it working I tried to remove the KMH and connect the False leg to the next action I get the error in the second screen shot. “There are duplicated action connectors: onFailure”
What gives? I cannot save this event no matter what I do including removing the first condition and putting it back in, removing both connector legs and putting them back. If I close the event without saving it continues to work with the KMH in the action path.
Also, has anyone heard of improvements to the error checking that would select the action or connector that is causing the issue when it says there is an error?
It seems like the connectors don’t like to be moved around and reconnected. It used to just not work at all, now it seems to work some of the time. I would try deleting the message handler and saving and closing the eventto see if you can get that change to stick. Then go back into the condition and add the next step by clicking false in there.
I had this issue last week I think. In my case when I select various connectors the connection type in the right hand properties pane did not match what was shown on the graph. I had to change them all in the properties panel, which took a while as some of them kept reverting each time I saved. But eventually I prevailed and the error was gone.
I had this issue in another event where I tried to add a condition at the beginning of the event and it threw this error. What does not make sense is that it is saying that “There are duplicated action connectors: onSuccess” and there are no onSuccess connectors on a Condition and that is what I am changing.
So I tried what @Evan_Purdy said and this is what I found. When I connected the False leg of the first Condition (another bug can’t save the shape label) to the second Condition ALL of the subsequent Condition True legs were switched to False in the properties pane except the first Condition (last snap shot).
I was able to save the event after resetting the True legs back to True in the Properties pane and was able to save. Thank you @Evan_Purdy!
This is reproduceable how do we submit for a fix? I tested deleting/adding the False leg on the first Condition again and the error reoccurred. I was able to save after resetting the second two Condition True legs to True again, happens ever time.
If you can make a reproducible case for them, go for it man! I wasn’t sure wtf happened since I couldn’t find anyone else talking about the issue, but I see you having it now. Maybe its new for this latest update.
You have to make a case in Epicare, they will probably want your layer, or a simplified demo layer, or to do a webex, or a list of steps to reproduce, etc..
