Troubleshooting
This guide helps you resolve common issues with notification templates.Template Validation Errors
Syntax Error: Invalid Handlebars Syntax
Error Message: “Invalid Handlebars syntax” or “Unexpected token” Common Causes:-
Unbalanced brackets
- Every
{{#if}}needs a closing{{/if}} - Every
{{#each}}needs a closing{{/each}}
- Every
-
Incorrect helper syntax
- Verify helper names are spelled correctly
- Check that parentheses are balanced
-
Missing quotes in string attributes
- String values must be quoted
- Use the Validate button in the template editor before saving
- Check brackets are balanced: each opening has a closing pair
- Verify helper names match exactly (case-sensitive)
- Add quotes around string values in helper attributes
Max Length Error: Template Exceeds 10,240 Characters
Error Message: “Template body exceeds maximum length” Common Causes:- Template is too comprehensive
- Too many examples or detailed change descriptions
- Large data structures being displayed without filtering
-
Simplify the template
- Remove unnecessary formatting
- Remove comments
- Use shorter variable names where possible
-
Use the
limithelper -
Show summaries instead of details
-
Remove conditional sections for optional data
-
Split into multiple templates
- Create separate templates for detailed vs. summary views
- Use different templates for different entity types
Field Name Not Recognized
Error Message: Template doesn’t render field, shows empty string Common Causes:- Incorrect property path
- Property doesn’t exist for this entity type
- Typo in property name
-
Verify property names
- Check Template Context Reference
- Use dot notation:
entity.owner, notentity.owner_name
-
Use conditionals for optional fields
-
Check for property availability by entity type
Notifications Not Rendering Correctly
Notifications Look Garbled or Misformatted
Symptoms:- Text appears without line breaks
- HTML tags visible in notification
- Formatting looks different on different channels
- HTML is malformed
- Characters aren’t escaped properly
- Channel-specific formatting issues
-
Validate HTML
- Ensure all HTML tags are properly closed
- Use standard HTML tags (not XHTML self-closing unless valid)
-
Use the Preview feature
- Preview shows how template renders with sample data
- Check preview across different channel types
-
Send test notifications
- Test to your actual Slack/email/Teams channels
- Verify formatting in each platform
-
Check special characters
- Characters like
<,>,&need escaping in HTML - Use
<,>,&instead
- Characters like
Template Selected But Not Showing
Symptoms:- Notifications are sent but template isn’t being used
- Using default formatting instead of custom template
- Template not selected in subscription
- Subscription is inactive
- Event type doesn’t match what subscription is listening for
-
Verify template is selected
- Go to Settings > Notifications > Subscriptions
- Edit the subscription
- Confirm the Notification Template dropdown has your template selected
- Not just blank
-
Check subscription is active
- Enable/activate the subscription
- Verify it’s not disabled
-
Verify event types match
- Subscription must be listening to entity updates that match your template
- Example: Template for tables won’t be used for dashboard updates
Missing Data in Notifications
Template Shows Empty Values
Symptoms:Owner:appears with no value- Sections are blank even though field should exist
- Links or data don’t appear
- Data doesn’t exist for this entity instance
- Property name is different than expected
- Data is nested differently
-
Use conditionals to handle missing data
-
Check property availability
-
Verify nested properties exist
If a field is missing, the template renders an empty string. Always use conditional logic to prevent empty sections.
Change Data Not Displaying Correctly
Symptoms:- Updated fields showing as empty
- Can’t see what changed in the notification
- Not using
groupEventChangeshelper - Trying to access raw change description
groupEventChanges to organize change data:
Link and URL Issues
Links Don’t Work or Point to Wrong Place
Symptoms:- Clicking link in notification shows 404 error
- Link goes to wrong entity
- Incorrect entity type in URL
baseUrlis not configured- Entity IDs have changed
-
Use
buildEntityUrlhelper -
Verify
baseUrlis set- The system should automatically set
baseUrl - Check if your Collate URL is configured correctly
- The system should automatically set
-
Test links
- Send test notifications
- Click links and verify they work
Helper Issues
Helper Not Found or Returns Wrong Result
Symptoms:- “Helper not found” error
- Helper name is red/underlined in editor
- Results are unexpected
-
Misspelled helper name
-
Wrong number of arguments
-
Arguments in wrong order
- Check Custom Helpers Reference
- Verify exact helper name and argument order
- Use Preview to test
Best Debugging Practices
1. Use Preview Frequently
In the template editor, click Preview to:- See how template renders with sample data
- Catch formatting issues early
- Test across different channels
2. Send Test Notifications
Click Send Test to:- Send to real email/Slack/Teams
- Verify how it actually appears to users
- Test with your actual notification setup
3. Start Simple
When building templates:- Start with basic template
- Add features one at a time
- Test each addition
4. Ask for Help
Provide:- The template code
- What error or unexpected behavior occurs
- What data you expected to see
- Screenshots of Preview/test results