List all invalid / broken triggers in the Trigger errors modal

Product Suggestions
, , , ,
1

Greetings.

Currently (and if I’m not mistaken), only the connector function triggers and function triggers seem to be listed in the Trigger errors modal.

This modal is very useful since it allows to fix broken triggers. For example, I had a Run Device Function > Light Kit > All bins off trigger that didn’t work since it was referring to a deleted device. Unfortunately I had no trace of this in the Trigger errors modal. Since the app was built by someone else, I had absolutely no idea such a problem existed.

I suggest that all triggers that are undoubtedly invalid/broken at app building time are listed in this modal. This obviously excludes runtime trigger errors (such as an unreachable network device).

Typical use cases arise when an app is about to be reviewed / published and the app builder must make sure:

  • no trigger throws an error,
  • that all trigger actually do what they are supposed to
  • and that no trigger is not executed due to a previous trigger raising an error.
2

Hey @fti thanks for the feedback, really appreciate you flagging this!

You’re right that the Trigger Errors modal today only surfaces errors from functions and connector functions. That was intentional at launch - the modal was built specifically to simplify change management around the inputs and outputs of function shapes, which was the most common source of breaking changes we were hearing about.

That said, we know it’s not the full picture. We’re planning to extend the modal to cover more trigger failure modes later this year, and I’ll make sure this thread gets factored in as we start scoping that work.

Thanks again for taking the time to share this.

Pete