When a notification isn't received as expected, it is likely something is configured incorrectly in:

Notification Reports are used to review historical notification activity, not to configure delivery behavior, so they would not cause a notification to fail.

The configuration database stores system-level settings and is not a typical point of failure for an individual notification not being received.

The notification template in Archer defines the trigger conditions, recipient logic, message content, and delivery settings for a notification. A misconfiguration in any of these elements - such as an incorrect condition, wrong recipient field, or disabled status - will prevent the notification from being generated or sent. Because the template drives the entire notification workflow, it is the primary area to inspect during troubleshooting.

While the supporting application provides context for the notification, the template configuration - not the application itself - governs whether and how the notification is sent.