FRONTSTEPS Violation Letters Not Sending: Troubleshooting Checklist

Violation letters in FRONTSTEPS usually fail to send because delivery is not enabled, the letter template or trigger is misconfigured, the owner record has no valid delivery method, or the item is stuck in a queue/approval step. Check the sending method, template mapping, recipient data, and the outbox/history to see where it stops.

 

Fast checks that fix most cases

 

• Confirm the violation is eligible to send: the violation must be in the correct status (for example “Open/Active”), have a category/type that matches a letter rule, and not be marked resolved/closed.
• Check the delivery method: if set to Email, the homeowner must have a valid email and be opted in; if set to Print/Mail, the address must be complete; if set to Portal, the owner must have portal access enabled.
• Verify the letter template is assigned: the correct template must be linked to the violation type/stage (first notice, second notice, hearing, etc.). A template can exist but not be mapped to the rule.
• Look for an approval/hold: some setups require manager/board approval before sending. If approval is required, the letter will sit in a pending state and never send.

 

Where it usually breaks (and what to check)

 

• Email sending settings: confirm the community/company email configuration is active (sender address, permissions). If emails are sent “on behalf of” a mailbox, that mailbox must allow it.
• Bounced or blocked emails: check communication history for bounced, blocked, or suppressed. “Suppressed” means the system stops trying after repeated failures.
• Recipient selection: confirm the letter is addressed to the correct party (owner vs tenant). If the system is set to send to “Primary Owner” and that field is blank, nothing sends.
• Merge fields failing: templates use merge fields (auto-filled placeholders like owner name, address, violation date). If a required field is empty, the document may fail to generate.
• Queue/outbox: check the outbox/batch/print queue. If it is in “Generated” but not “Sent,” the final send step was not completed.

 

If everything is correct but it still won’t send

 

• Send a test to one record: create a new violation on a test unit with a known-good email and try sending one letter. If the test works, the issue is data on the original owner/unit.
• Rebuild the template: duplicate the template, remove complex formatting, re-add merge fields, and re-map it. Corrupted formatting can stop generation.
• Check user permissions: the user must have rights to generate/send letters. Missing permission can look like “nothing happens.”
• Escalate with proof: provide support the violation ID, community, template name, time attempted, delivery method, and any error text from history/logs. Ask them to check mail/email service logs and document generation errors.