Why is my notification still Pending?
A Pending notification is queued for delivery or is currently being retried.
Check that:
The Notification Router flow is running.
The relevant channel adapter flow is running.
Connection references use a valid, licensed account.
Component Health does not show a Router or adapter failure.
The Monitoring dashboard does not show an elevated Pending queue.
The Monitoring dashboard can flag an elevated Pending queue when more than 100 notifications remain Pending for more than 10 minutes, based on the default dashboard threshold.
Why has my notification Failed?
A notification receives the Failed status when delivery does not succeed after the available retries and fallback channels have been exhausted.
Check:
Error Details
Retry Count
The selected delivery channel
The recipient's Max Retries
The recipient's Channel Priority
Component Health for the relevant channel adapter
After resolving the underlying issue, an administrator can reset the notification to Pending to trigger redelivery.
Why did my notification fail without any retries?
Check the recipient's Max Retries setting.
If Max Retries is set to 0, vNudge does not retry the current channel before moving to the configured fallback channel.
This is expected behaviour and allows users to opt out of same-channel retries.
Why is my notification Suppressed?
A notification is Suppressed when the recipient has Mute All enabled in their Notification Preference.
When Mute All is enabled, delivery is skipped and no channel adapter is invoked.
Check the recipient's Notification Preference and disable Mute All if future notifications should be delivered.
Suppressed notifications are not considered delivery failures.
Why is my notification Blocked?
A Blocked notification indicates that the organisation's product licence was invalid when the Router attempted to dispatch the notification.
To investigate:
Review the licence information in the Monitoring dashboard.
Resolve the licensing issue.
Select Refresh License.
Confirm that the licence is valid.
Reset affected notifications to Pending if redelivery is required.
Blocked is a terminal status. Blocked notifications are not automatically retried.
Why wasn't a fallback channel used?
vNudge attempts the next channel in Channel Priority after the current channel's retry allowance has been exhausted.
Check:
Max Retries
Channel Priority
The notification's Retry Count
The notification's Error Details
Retries use an increasing delay:
First retry: 30 seconds
Second retry: 60 seconds
Third retry: 120 seconds
If Max Retries is set to 0, vNudge skips same-channel retries and proceeds directly to the next configured fallback channel.
Each fallback channel receives its own retry allowance.
Why isn't a user receiving notifications?
Check that:
The user has the appropriate vNudge security role.
The vNudge application is available to the user.
Mute All is not enabled.
The selected channel meets the recipient requirements.
The notification is not Suppressed or Blocked.
The relevant channel adapter is healthy.
Also check whether the user's Notification Preference is Active.
Only an active Notification Preference is used for delivery. If the preference is inactive, its Preferred Channel, Channel Priority, Secondary Email, Mute All, and Max Retries settings are ignored.
If the notification does not specify a channel and there is no active Notification Preference, vNudge uses Email.
Why is Email delivery failing?
Check that:
The recipient has a valid email address or Secondary Email.
The Email Adapter is healthy.
The Office 365 connection reference is configured.
The connection account is valid and licensed.
If a Secondary Email is configured on an active Notification Preference, vNudge uses it for Email delivery.
Why is Microsoft Teams delivery failing?
Check that:
The recipient has a user principal name or email address registered in Microsoft Teams.
The Teams Adapter is healthy.
The Microsoft Teams connection reference is configured.
The connection account is valid and licensed.
Microsoft Teams delivery supports one-to-one chat messages.
Why is In-App delivery failing?
Check that:
The recipient has access to the relevant model-driven application.
The In-App Adapter is healthy.
The notification's Error Details do not indicate a recipient or application-access issue.
Why can't I activate a Notification Rule?
Review the validation error recorded against the Notification Rule.
Common validation issues include:
No recipient is configured.
Subject or Body is missing.
The Target Entity does not exist.
A Watched Attribute or condition field does not exist on the Target Entity.
A Lookup recipient path contains more than two lookup hops.
A Lookup recipient path contains an invalid lookup attribute.
A Lookup recipient path does not resolve to a Dataverse system user.
The changed condition is used with a Create-triggered rule.
Correct the configuration, save the rule, and activate it again.
If activation fails, a Draft rule remains Draft and an Inactive rule remains Inactive.
Why can't I edit an Active Notification Rule?
Notification Rule configuration is locked while the rule is Active.
Deactivate the rule before changing its:
Target Entity
Watched Attributes
Trigger Type
Conditions
Recipients
Delivery Channel
Subject or Body
After making the required changes, save and reactivate the rule.
vNudge validates the rule again before it returns to Active.
Why isn't an Active Notification Rule creating notifications?
Check that:
The rule is Active.
The rule is monitoring the correct Dataverse entity.
The required Watched Attribute changed for a Change rule.
All configured conditions were met.
At least one recipient resolved to a Dataverse system user.
Important
If none of the configured Lookup recipients resolves to a Dataverse system user, vNudge skips the rule. No notification is created and no error is recorded.
Why does a component appear stalled?
A component can be identified as stalled when it has never succeeded or its last successful execution is older than the configured stale window.
The default stale window is 60 minutes and can be configured for the environment.
In a newly deployed environment, a component may not yet have processed notification traffic. Review Component Health and refresh the dashboard after the component has run.
Where can I see more information about an issue?
Use the Monitoring dashboard to review:
Active Problems
Notification delivery status
Channel Breakdown
Component Health
Retry Distribution
Registered Evaluation Steps
For individual notification failures, review the notification's Error Details, Retry Count, status, and selected delivery channel.
If the issue cannot be resolved using the information above, see Support for the information to provide when escalating the issue.