When a trigger-based action is configured to send a message, if the recipient doesn't have the appropriate permissions, the notification attempt will silently fail.

+
+I’ve been bit (silently) by permissions causing lack of notification at least twice. Everything seemed right configuration-wise, but the notification wasn't being sent. I was stumped.

Generally, silent failures are a “bad thing”.  So I checked with Zabbix support to see if a message is logged anywhere - they said it isn't. 

If there’s code to check whether the user has access, then couldn't code simply be added to write out to the log when such a case occurs?

Is it an expected use case for a Zabbix admin to rely on host permissions to decide whether or not an action should happen?
I would argue “no”, and that when this happens it’s usually due to human error. The whole point of creating an Action is to let certain people know when certain triggers are fired on certain hosts. So relying on permissions to silently stop the action seems much more obscure than configuring the action’s Conditions to match only the desired hosts.

So if this scenario is most often caused by a mistake, wouldn’t it make sense to allow an admin to “catch” that mistake? And wouldn’t the simplest way be to just log an error?