At Boltrics, our support team doesn’t just aim to solve tickets—they aim to deliver solutions that empower you. Every day, they tackle a wide range of issues, from straightforward fixes to intricate problems that demand creative problem-solving.

While we hope your systems have run smoothly this year, we know that occasional hiccups are inevitable. And when that happens, our support team is ready to get you back on track as quickly as possible. But did you know many of the challenges you face are shared by other logistics service providers? By addressing these recurring questions, we aim to make your operations more efficient and stress-free. 

The #1 support question in 2024

This year, Job Queues in Microsoft Dynamics 365 Business Central took center stage in support inquiries. These powerful tools keep your processes running automatically but can become a challenge when they fail. In this blog, we’ll guide you through common issues, highlight best practices, and share updates to help you master Job Queues in 2025. 

 
1. Job Queues Failing: How to Identify Errors and Restart 

When a job queue fails, it’s critical to identify the error quickly and take steps to restart the process. Here’s how you can do this: 

  1. Navigate to the Job Queue Entries page in Business Central. 
  2. Select the specific job queue entry. 
  3. Use the Log Entries action to view detailed error messages and show the Error call stack. 

After identifying the issue, you can restart the job queue by setting its status first to OnHold then to Ready. This ensures the job resumes its automation without further delays: 
 

2. Changes to Restarting Failing Job Queues 

In earlier versions, Job Queue 8 was a custom solution developed by Boltrics to reset the status of failing job queues from Error to Ready. However, this method has been deprecated. 

We now recommend utilizing Microsoft’s standard functionality to manage failing job queues. This involves monitoring and reattempting to run failing job queues directly through the Job Queue Entry Card interface: 

This updated approach offers greater control and flexibility in managing your Job Queues. To make the most of it, keep the following recommendations in mind: 

  • Maximum No. of Attempts to Run 
    Set this value to a number between 1 and 10. Avoid using 0, as it will cause the job queue to fail immediately without any retries. Choose this value carefully, balancing the need for retries with system performance considerations. 
  • Rerun Delay
    Ensure that the Maximum No. of Attempts to Run, multiplied by the Rerun Delay (sec.), does not exceed the configured No. of Minutes between Runs. This ensures that retries are spaced appropriately without conflicting with the next scheduled run. 

By adhering to these recommendations, you can avoid unnecessary failures while maintaining an efficient job queue schedule. 

3. Best Practices for Configuring Job Queues 

Proper configuration is key to ensuring your Job Queues run smoothly. Here are some practical tips: 

  • Optimize Recurrence Settings: Schedule recurring tasks at intervals that align with your business needs while minimizing the impact on system performance. Reserve the 1-minute interval between runs only for critical Job Queue entries that require frequent execution. For all other tasks, consider longer intervals to reduce system load and ensure smoother operations 
  • Leverage Job Queue Category Codes: Categorize job queues using codes to prioritize tasks and prevent conflicts. For example:  
  • Use the category code DH for Document Handling (e.g., Job Queues 2 and 3). 
  • Use the category code DI for Data Integration (e.g., Job Queues 17 and 18). 

Setting a Job Queue Category Code goes hand-in-hand with assigning a Priority value. This ensures that dependent jobs run in the correct sequence and avoids potential conflicts. 

For detailed guidance, check out Microsoft’s documentation on Job Queue scheduling

4. Receiving Notifications for Job Queue Issues 

When Job Queues fail, receiving timely notifications can make all the difference. Here are two ways to stay informed: 

Option 1: Boltrics-Specific Method 

Use Job Queue 15 to send notifications when an issue arises. Simply define an email address in the DI settings, and you’ll receive alerts whenever a problem occurs. 

Option 2: Microsoft Standard Notification System 

Microsoft’s built-in notification feature allows you to get alerts about background processing issues. This helps you react quickly and resolve issues efficiently. For more details, check out these new features: 

Wrapping It Up 

Job Queues are a vital tool for automating and streamlining your processes in Microsoft Dynamics 365 Business Central. By addressing common issues, leveraging best practices such as Category Codes and Priority Settings, and staying informed through notifications, you can ensure these automations run efficiently throughout 2025. 

If you encounter any issues, we recommend the following steps: 

  1. Review these recommendations carefully. 
  2. Implement any necessary changes. 
  3. Restart the Job Queue. 

If the issue persists, please submit a support ticket with the following details to ensure swift assistance: 

  • Job Queue Entry Name and Task No. 
  • Exact Date/Time when the issue started occurring. 
  • Error Message or Call Stack (if available). 

Our support team is always ready to assist. Together, we’ll keep your operations running smoothly and your business processes optimized!