Problem with 'Clone' with 'Cloud end point' trigger

šŸ“ Rule MachineĀ®
1

I had an app with a 'Cloud end point' for a trigger that I cloned to make a new app.
The 'cloud URL to trigger' for the new clone was identical to the one for the original app.
I tried deleting the trigger on the new one and creating a new 'Cloud end point' trigger but it also was identical.
I had to delete the clone and create a new app from scratch to get a new, proper 'cloud URL trigger'.

While I'm at it, I often use clone to make temporary copies of apps while I'm writing them.
Unfortunately, all the clones for 'Wiget' are named the same: Widget copy.
Sure would be nice if they were Wiget copy 1, Wiget copy 2, Wiget copy 3, etc.
Also, would be nice if the clones were paused when created to prevent surprise execution of apps with the same triggers.
While you're at it... :worried:
Could you generate an error when creating a new app with the same name as an app that already exists? Two apps with the same name is confusing.
Just saying... :wink: :grinning: :wink:

2

Reopening an old thread which I am surprised was not closed. I have run into the issue of it copying the same cloud end point when you clone. But it doesn't do it anymore so I am assuming it was fixed at some point.

I agree with all of the other suggestions. Adding one to this I would like the clone, export, run, etc. commands be added to the rule list so that you don't have to open the rule then click through multiple screens to accomplish some of these actions. Especially as opening rules is a slow process for me as my hub is quite slow when editing due to the number of rules I have.

3

Perhaps it would help if you knew that cloning an app, in and of itself, has no understanding of how the app works or what it might need as a clone. All itā€™s doing is copying certain data structures common to all apps. The responsibility for what happens is entirely in the userā€™s hands. If you want a paused clone, simply pause the rule you want to clone before cloning.

Yes, this topic should have been closed, and will be now.

2 Likes