Remove reference to cloned recipe

[AMacourek]

I cloned a recipe and made significant changes.  I noticed in settings there is a message: "The parent recipe that this recipe was copied from has a new version. Installing this new version overwrites the current recipe. Installed updates can be reverted via recipe version history." with an Install button.  A person could click this and overwrite the recipe.

Why would you want this feature?  In my view, cloning a recipe would be the same thing as "Save As."  Why would you want to propagate changes to all other recipes that started from one?

My question is how to remove a reference for a cloned recipe?  

[RussellJ]

Gah! I KNEW IT! Sounds like an easy fix and hasn't taken too much time to date - there are only 3 Functions I've doubled up.  But pleased to know there's a proper way to do this.  It felt dirty 😀  Thanks @gary1 

[gary1]

The recipe lifecycle management tool is also really helpful if you're deploying recipes across multiple environments. Probably overkill for this situation, but maybe worth a look in the future.

[mppowe]

I'll pile on to the topic... I talked to Workato years ago about this behavior where Cloning a recipe implied a connection. They said the functionality was assumed to be like a "template", where you have a template recipe from which you're cloning.

But that's never really been my Use Case... I've always wanted to copy a recipe just to give me a starting point from other common approaches and then change the unique parts.  So I've always followed the same steps that gary mentioned, copy 2x and delete the middle one.  Annoying but not a big deal.  

To be fair, I've never tried to accept the update from a copied recipe, so maybe it's really surgical and useful, but have never bothered.