Business Central 2024 wave 2 (BC25): Get external notifications when job queue entries fail (Set up new Job Queue notifications)

Dynamics 365 Business Central

Hi, Readers.
Dynamics 365 Business Central 2024 wave 2 (BC25) is generally available. More details: General availability: Dynamics 365 Business Central 2024 release wave 2 (BC25).

I will continue to test and share some new features that I hope will be helpful.

There are two release plans that mention this new feature.
Get external notifications when job queue entries fail and Get notified about issues with job queue background processing:

Business value:
Sometimes tasks, reports, or batch processes can take a long time to complete. To keep people productive in the meantime, companies often use Business Central’s job queue to run processes in the background. If something goes wrong and an important background process stops, or isn’t scheduled for some reason, being notified about the issue can help you react quickly to resolve it.

https://learn.microsoft.com/en-us/dynamics365/release-plan/2024wave2/smb/dynamics365-business-central/get-external-notifications-when-job-queue-entries-fail?wt.mc_id=DX-MVP-5004336

With this wave (BC25), we have a new way to send information when Job Queues are failed in Business Central. Let’s see more details.

To be notified when there are issues with job queue processing, you can run the Set up Job Queue Notifications assisted setup guide from the Assisted Setup page now.

Set up Job Queue Notifications
Set up Job Queue Notifications to receive notifications when jobs are failed.

PS: In BC24.5 and previous versions

Choose Next on the Set Up Job Queue notifications page.

Set up the users to notify about issues with job queue entries. You can choose whether to notify the user who started the job queue entry by turning on the Notify the user who initiates background tasks toggle. You can also choose to notify job queue notification administrators by turning on the Notify these job queue notification administrators toggle and choosing users in the list.

Notify the user who initiates background tasks
Specifies whether the user who initiates a background task should receive a notification when the task is failed.

Notify these job queue notification administrators
Specifies whether these job queue notification administrators should receive a notification when any task is failed in Job Queue.

Choose Next on the second step to specify how to send notifications. You can choose whether to use in-product notifications on home pages by turning on the In-product notifications toggle.

In-product notifications
Specifies if the notifications should be displayed in the Business Central web client.

Control notifications with business events (preview)
Specifies if the external business event will be enabled.

Choose When do you want to display in-product notifications? You can choose to notify users immediately with in-product notifications on their home pages by turning on the Immediately for each job queue entry toggle or, to reduce the noise, you can choose to notify users when failure thresholds are exceeded by turning on the After a threshold is reached toggle. Use the Low threshold and High threshold fields to define how many times a job queue entry must fail before notifying a user.

Immediately for each job queue entry
Specifies the user should receive a notification once the task is failed.

After a threshold is reached
Specifies the user should receive a notification when the count of failed jobs reach the low threshold.

Choose Next on the fourth step to complete the guide and Finish to apply the notification settings.

After the guide completes, if you chose Notify the user who initiates background tasks, the notification is enabled for all users on the My notifications page.

If a user doesn’t want to receive these notifications, they can turn off Job Queue Failed Notification on the page.

For example, I set up a Job Queue that is bound to go wrong.

Below is the error message.

The Job “Sales-Post” scheduled by ADMIN experienced an issue.

And user home pages contain three new cues that inform them of the current state of the job queue entries they started:

  • Tasks Failed shows the number of job queue entries that failed.
  • Tasks In Process shows the number of job queue entries that are in progress.
  • Tasks in Queue shows the number of job queue entries that are waiting to start.

Each user can further set up the visual appearance of these cues by choosing the Set up cues action in the Job Queue Tasks part of the home page. The Set up Job Queue Notifications guide only sets Tasks failed thresholds.

You can also choose Create an automated flow from Job Queue Notification template to open the Job Queue Entries page.

Then on the Job Queue Entries page, choose AutomatePower Automate, and then Create automated flow to open the Create a flow page.

The Create a flow page contains a Notify on Outlook or Teams when Job Queue in Business Central fails template

Here are the details about this template.

PS: This template is not available in BC 25.0 Public Preview. Please test it in the BC 25.0 official version.

Test:

In addition, since Business event (Job queue task failed – 1.0) is already available, so we can also create a flow ourselves.
PS: Dynamics 365 Business Central: OnValidate (Field) Trigger in Power Automate (Trigger a flow when a field is modified) – Business events

For example,
Step 01: Business Central -> When a business event occurs (V3)

Step 02: Business Central -> Get record (V3)

Step 03: Teams -> Post message in a chat or channel

Test:

To sum up briefly, in this wave (BC25), Microsoft provides three new ways to send notifications when job queue entries fail.

  • In-product notifications (in the Business Central web client)
    • Job Queue Failed Notification on the page
    • Job Queue Tasks part of the home page
  • Control notifications with business events (preview)
    • Send external notifications through tools such as Power Automate

Great, give it a try!!!😁

END

Hope this will help.

Thanks for reading.

ZHU

コメント

Copied title and URL