When pasting copied triggers, disable them by default

[sebme]

Please consider changing the behavior that causes a pasted trigger that has been copied from somewhere else to be immediately activated.

Alternatively, add an option to the trigger editor window that would allow to enable/disable a trigger prior to saving it.

[OlgaStroilova]

Thank you @sebme for the feedback.

Could you elaborate your use case and the user flow a bit? What goes wrong when the trigger is active by default, and what would you do if it was deactivated after getting copied in?

This is helpful for two upcoming projects - Functions and the App Trigger Revamp, that were mentioned in a previous post last week:

I wish there was a method to pull up the connector function from the edit trigger page

Hi @mellerbeck, Thank you for the feedback. This is a pain point we’re aware of, and I’ll make note of the upvote for two upcoming projects - in early 2025 we’re planning work on App Functions (ability to create and reuse trigger logic more broadly, including connector functions called via a trigger). Here, we’re planning to eventually allow a way to click through to the Function definition. Likely we could reuse that same design pattern for Connector Function clickthroughs. later in 2025…

• Olga

[sebme]

It is simply meant to give the developer the ability to add a trigger function without immediately arming it. This is particularly useful for emergency edits where you need to inject something but can’t just hold the entire line to make the edit.

[OlgaStroilova]

Gotcha… Are you editing a live Application while Operators are also using it in Development mode? Is the concern that it will fire before you have a chance to disable it, or that the editor would forget to disable?

Sharing all the feedback for our 2025 App Triggers revamp project, so good to know the tradeoffs between having to go through and enable many triggers after copying every time - vs disable in what feels like a more rare use case.

[danielpomeranz]

I would argue against changing the default here, this would frustrate me as 99% of the time if I am adding a trigger I want it to be active so this would be just one more click every time.

Alternatively, add an option to the trigger editor window that would allow to enable/disable a trigger prior to saving it.

This I agree, the toggle should be available from the trigger window

[sebme]

Correct. That would be the main concern here, not being able to have people not accidentally firing it right away. This especially applies to “pass-through” steps where stuff is “auto-firing” and a step acts just as a transition.

To @danielpomeranz point, the current default being “on” is fine… but it would be nice to at least have the option to set it to “off” right at the time when you create it in the editor.