Skip to main content

Violation emails not going out (troubleshooting guide)

If your violation notification emails are not going out, here are some important points and settings to check based on the OPSCOM system:

  • Ensure the user is the primary driver and has an email address set in the system. Violations connected to the primary driver with a valid email are automatically sent an email with AutoNotice=1. If no email exists, the violation is flagged for a letter report with AutoNotice=2.
  • Verify the system tasks are running properly. The sending of violation notices depends on the "New Violation Notices" system task being enabled and run either on schedule or manually via Tools > View System Task Logs.
  • Check that the notice-related settings are properly configured:
  • The violation days until due setting in Tomahawk Options > System Settings.
  • System Settings → Collections → Include All Unpaid Violations to manage which violations are included in notices.
  • If sending warnings, confirm the "Send Notices For Warnings" setting is enabled under System Configuration > System Settings > Violations.
  • Confirm email templates for violation notices are properly set up under System Configuration > Content & Designs > Email Templates.
  • Check for any notices stuck or not sent by reviewing the letter report (Violations > Letter report), especially for users without an email address.
  • Lastly, confirm that no filters or additional restrictions are preventing notifications of older violations (only violations issued the same day are notified by email as new; older ones may not notify).

Make sure to review these configurations, run the relevant system task, and verify the recipients have valid email addresses to ensure violation notification emails are generated and sent successfully.

Back to top