Can't get notifications to fire for scoped application

[Ed41]

I am building a scoped application and need to have the application generate email notifications at specific points in the workflow.  So far I have tried configuring the triggers in the notification itself, triggering the notification via an event (fired off the workflow), and the "notification" activity within the workflow editor itself.  None of these are triggering emails.  The notification and workflow are in the same application scope, and I'm not seeing any cross scope errors in the logs so I'm not sure what I missed.  Is there some kind of cross scope access I need to configure to allow notifications to fire from a scoped app?

[Pintu2]

Can you try checking these:

1. Have you enabled system Email properties? 

2. Have you created a notification and added the event details in the notification and in the workflow? And is there anything you could check in event logs/email logs.

[Ed41]

Yes, e-mail is enabled in email properties.  There is no email created in any mailbox (outbox, sent, skipped, etc) regardless of how I try to trigger it.  The email logs don't show any record of a mail being created either.  It's as though the email is not being triggered regardless of how I attempt to send it, which is why I started looking at cross-scope issues.  I have so far done the following:

Created a notification that triggered on insert of a record in the table used by the scoped application based on conditions.  The notification is in the same scope as the workflow.  No e-mail was generated.

Modified the above notification to instead use an event as a trigger.  The event was triggered by an activity in the workflow itself.  The event was triggered successfully and shows in the event queue as processed, but no e-mail was generated.  The event queue is in the proper scope.

Created a notification directly in the workflow itself using a notification activity.  I did this primarily to test whether it would send an e-mail or not, and no email was generated.

[Ed41 · Accepted solution]

It turns out the issue here was either the content of the notification or the fields being used to dictate who should receive the notification.  cleaning both of those out and putting in plain text allowed the notification to fire as expected.  I'm not sure exactly what content was causing the problem, but now I can add things one at a time to find out what was going wrong.