Skip to main content

Email Configuration

Configure email notifications to receive job failure alerts via email. Email notifications use Business Central's built-in email system and require no additional infrastructure.


Prerequisites

Before configuring email notifications:

  1. Email Account Configured: BC must have at least one email account set up

  2. SMTP Access: Your email account must be able to send emails

  3. Job Queue Admin Setup Complete: Privacy acknowledged and extension enabled

Verify Email Setup

  1. Search for Email Accounts

  2. Verify at least one account exists and is set as default

  3. Test sending an email from BC

If no email account exists, configure one before proceeding.


Creating an Email Channel

Step 1: Open Notification Channels

  1. Search for Notification Channels

  2. Or from Job Queue Admin Setup: Actions > Navigate > Notification Channels

![Screenshot 2026-02-08 173634-20260208-153634.png](/img/job-queue-admin/Screenshot 2026-02-08 173634-20260208-153634.png)

Step 2: Create New Channel

  1. Click New to create a new channel

  2. Fill in the required fields:

FieldValue
CodeUnique identifier (e.g., EMAIL-OPS)
Channel TypeEmail
DescriptionDescriptive name (e.g., "IT Operations Email")
Email AddressDestination email address
EnabledYes

image-20260208-154833.png

Step 3: Save and Test

  1. Click OK to save the channel

  2. Use Send Test Notification action to verify delivery

  3. Check your email for test notification


Email Channel Fields

Identification

FieldDescriptionRequired
CodeUnique channel identifierYes
Channel TypeMust be "Email"Yes
DescriptionHuman-readable nameNo
EnabledActive/inactive toggleYes

Email Settings

FieldDescriptionRequired
Email AddressRecipient email addressYes

Email Address Format:

  • Single address: admin@company.com

  • Multiple addresses: admin@company.com;ops@company.com (semicolon-separated)

  • Must be valid email format

  • Distribution lists supported


Email Message Format

Subject Line

[JQA] Job Failed: {Job Description}

Message Body

Job Queue Failure Notification

Job: {Job Description} Error: {Error Message} Time: {Failure Timestamp} Company: {Company Name}

Object: {Object Type} {Object ID}

View Job: {Deep Link URL}

Example Email

Subject: [JQA] Job Failed: Process Sales Orders

Job Queue Failure Notification

Job: Process Sales Orders Error: Connection timeout while connecting to external service Time: 2024-01-15 14:30:45 Company: CRONUS International Ltd.

Object: Codeunit 50100

View Job: https://businesscentral.dynamics.com/...


Testing Email Channel

Using Send Test Notification

  1. Open the Email Channel card

  2. Click Send Test Notification in the action bar

  3. A test notification is sent immediately

  4. Check your email for the test message

image-20260208-160134.png

Using Validate Configuration

  1. Click Validate Configuration to check settings without sending

  2. Validates: email address format, BC email account exists

Verifying Delivery

  1. Check the destination inbox

  2. Check spam/junk folder if not received

  3. Review Notification Log for send status

Troubleshooting Test Failures

SymptomPossible CauseSolution
No email receivedBC email not configuredSet up Email Accounts
Email in spamFirst-time senderWhitelist sender address
Test failed errorInvalid email addressVerify email format
Timeout errorSMTP connectivity issueCheck email account settings

Multiple Email Channels

You can create multiple email channels for different purposes:

Example: Routing by Severity

Channel CodeEmail AddressTriggers
EMAIL-CRITICALoncall@company.comError, Cooldown
EMAIL-INFOitops@company.comAuto-Restart

Example: Routing by Team

Channel CodeEmail AddressDescription
EMAIL-SALESsales-support@company.comSales job failures
EMAIL-WAREHOUSEwarehouse@company.comInventory job failures
EMAIL-FINANCEfinance@company.comFinancial job failures

Use Job Configuration to route specific jobs to specific channels.


Best Practices

Email Address Selection

  1. Use distribution lists: Easier to maintain than individual addresses

  2. Avoid personal emails: Use team/role addresses

  3. Test delivery: Verify emails actually arrive

Trigger Configuration

  1. Start with Error only: Reduce noise initially

  2. Add Cooldown later: Important for persistent failure awareness

Maintenance

  1. Update addresses promptly: When team members change

  2. Review channels quarterly: Remove unused channels

  3. Test periodically: Ensure delivery still works


Common Issues

Emails Not Sending

Symptom: Notification Log shows "Pending" status

Causes:

  • BC Email Account not configured

  • Email sending disabled in BC

  • SMTP server issues

Solution: Verify Email Accounts setup in BC

Emails Going to Spam

Symptom: Emails received but in spam folder

Causes:

  • First-time sender

  • Email content flagged

Solution:

  • Add sender to safe senders list

  • Work with IT to whitelist BC email server

Invalid Email Address Error

Symptom: Channel test fails with validation error

Causes:

  • Typo in email address

  • Invalid format

Solution: Verify email address format (name@domain.com)


Next Steps: Consider adding Teams or Slack channels for instant notifications to your team collaboration tools.