Skip to main content

Why Are My Violation/Warning Notification Emails Not Going Out?

IfThis yourarticle newis designed to assist OPS-COM administrators in identifying and resolving issues preventing violation andor warning notification emails from being sent to users.

Purpose and Overview

When a violation or warning is issued in the system, OPS-COM can automatically trigger notification emails to the responsible party. If these notifications are not goingbeing out,received, pleasethis checkguide outlines the following:necessary configuration checks and system requirements to ensure email delivery functions correctly.

    Setup and Configuration

    To ensure emails are processed successfully, verify the following configurations:

    • User Information: Confirm that the user is marked as the primaryPrimary driverDriver and has a valid email address inassociated thewith system.their Emailsaccount. areThe sentsystem automatically sends emails to the primary driverdriver; with an email. Usersusers without an email address are instead flagged for letterLetter reports.Reports.

    • Confirm email

      Email Templates: Navigate to System Configuration then Content & Designs and click Email Templates to ensure that the templates for violation notices are properly configured properlyand underenabled.

    • System Tasks: Navigate to Tools then View System ConfigurationTask >Logs Contentto & Designs > Email Templates.

    • Verifyverify that the "New Violation Notices"Notices system task is enabled and running correctly (scheduledeither on a set schedule or manual)via inmanual Toolstrigger).

      > View System Task Logs.
    • Warning Settings: If you are sending warnings, ensurenavigate "to System Configuration then System Settings and click Violations. Ensure that the Send Notices For Warnings"Warnings checkbox is enabledenabled.

      under System Configuration > System Settings > Violations.
    • CheckNotice notice-relatedParameters: settings:

      Within
        Tomahawk
      • Options then System Settings, verify the Violation days until due inconfiguration. TomahawkAdditionally, Optionscheck >the SystemCollections Settings.
      • settings
      • Collectionsto >ensure Include All Unpaid Violations setting.is set according to your organizational requirements.


      Troubleshooting and Inspection

      If configurations are correct but emails are still not sending, follow these steps to investigate further:

      1. Navigate to Violations and select Letter Report.

      2. Inspect the letter report (Violationsto > Letter report) foridentify users withoutwho lack valid email addresses or who have unsent notices.

      3. KeepManually inreview mindthese thatentries to determine if they meet the criteria for automated notification.

      The system only newtriggers violationsinitial emails for New Violations (those issued on the samecurrent day). triggerExisting initialor emails. Olderolder violations may not automaticallytrigger sendan aautomated notification email.email after the initial issuance date has passed.


      Best Practices and Considerations

      • Maintain Accurate User Data: Regularly audit user profiles to ensure Primary Driver contact information, particularly email addresses, is up to date to prevent communication gaps.

  • ReviewingMonitor andTask correctingLogs: Periodically review the System Task Logs to confirm that automated processes are executing as expected without errors.

  • Consistency in Reporting: Use the Letter Report as a standard tool for identifying users who fall outside of the automated email criteria, ensuring these settingsindividuals andreceive runningnecessary thephysical relevantnotices.

    system
  • task should help resolve issues with violation notification emails not being sent.