When something doesn't work as expected (particularly with accessibility failures/flakiness), I often need to:

• Display a message to the user (e.g. talon.app.notify/actions.app.notify) explaining what didn't work and sometimes what to do to work around the problem
• Raise an exception so that the action stops execution

I either end up re-implementing the logic or just being lazy and only doing the latter.

Does it make sense to add a community action to do this, and/or a custom exception subclass?