When cloning a recipe, the new recipe should be disabled

Question

When cloning a recipe, the new recipe should be disabled

Opened this issue 8 months ago · 3 comments

When we clone a recipe, the clone keep the original recipe status in terms of "activation", i.e. if the recipe was enabled, the clone is enabled.

This shouldn't be the case because the clone needs by design to be updated before being requested, so it should be disabled automatically so that the scheduler might not pick it for scheduling.

Answer 1 · 2024-01-15T18:08:45.000Z

Pretty sure 5is was working that way in the past

Answer 2 · 2024-01-15T18:11:10.000Z

It has always worked like this. Definitely a regression. Could be pg-migration related but I believe I've cloned properly after that

Answer 3 · 2024-01-15T19:34:38.000Z

2 senior on this topic vs 1 junior, I can only admit you are right 🤣
Let's add a prio 1 tag then.