Small and medium business | Business Central, N...

data management

(6) Share

Report

Posted on by CD-12051622-0

Hi everyone,

I'm working on a Master Data Management (MDM) setup in Business Central SaaS, and I'm running into an issue with job queue entries crashing shortly after setup.

Here's our setup:
- One parent company (OPERATIONS) acting as the MDM source
- Multiple child companies pulling data from OPERATIONS via the native BC MDM module
- One child company (PARAM) configured as our template company

The problem:
I configured the MDM subscription in PARAM on April 30th around 4:50 PM. The job queue entries were created automatically (one per table — Customers, Vendors, Countries, Payment Terms, etc.), all running Codeunit 5339 (Integration Synch. Job Runner).

About 40 minutes later, the Customer sync job fell into Error status with the following message:
"A problem occurred and the task stopped. System updates or regular maintenance processes are probably the cause."

All other job queue entries then went into Suspended (inactivity timeout) status and never restarted automatically. As a result, no data changes made in OPERATIONS since April 30th were replicated to PARAM.

The job queue entries were running under a regular user account (not a dedicated service account).

My questions:
1. Is it expected that MDM job queue entries do not restart automatically after a crash or BC maintenance?
2. Is using a dedicated service account mandatory for MDM job queue entries to run reliably in BC SaaS?
3. Is there a recommended way to set up MDM job queue entries so they are resilient to BC automatic maintenance windows?

Thank you in advance!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (11)

Answers (0)

Sort by

Suggested answer

AndrewThomas81 2,228 on at

Like (3)

Report
Copy link

Link copied!

You can alter the maximum number of retries on any job queue entry, and setup notifications for when they fail. In my experience the MDM functionality is flakey, lacks features and is a pain to administer.

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hi, The standard method cannot automatically restart; this requires customization.

https://learn.microsoft.com/en-us/dynamics365/business-central/admin-job-queues-schedule-tasks#:~:text=If%20a%20job%20queue%20entry,Ready%2C%20or%20just%20restart%20it.

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 17,676 Super User 2026 Season 1 on at

Like (5)

Report
Copy link

Link copied!

Hello,
yes, this can happen: MDM creates recurring job queue entries per synchronized table, but if a job queue entry goes to Error, Business Central does not always just continue forever by itself; Microsoft’s guidance is to restart it manually, or use Maximum No. of Attempts and Rerun Delay (sec.) to reduce the chance that a temporary service/maintenance issue stops the job permanently. On Hold Due to Inactivity is different from a real error: MDM/sync jobs can sleep when there are no changes, and the next source-company change should normally reactivate them, but Microsoft also notes the user making the source change must have a BC license and permissions to reschedule the background task in the subsidiary; otherwise it waits for the unconditional sync controlled by Inactivity Timeout Period. A dedicated service account is not stated as “mandatory” in the docs, but it is a very good practice: use a licensed, non-personal account with the required permissions in all involved companies, make it the job queue user where possible, set retries/rerun delay, monitor Integration Synchronization Jobs, Job Queue Entries, and Job Queue Log Entries, and if the same “system updates or maintenance” crash repeats, send Microsoft/partner the job queue ID, timestamp, timezone, and call stack/log details.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 17,024 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

May this can help:

Automatic tasks not working? Discover the cause! - Nav24

Job Queue and Background Processing | MicrosoftDocs/dynamics365smb-docs | DeepWiki

The Most Frequently Asked Support Question in 2024: Job Queues in Business Central - Boltrics

Manage master data synchronization - Business Central | Microsoft Learn

Synchronizing Business Central and Dataverse - Business Central | Microsoft Learn

https://community.dynamics.com/forums/thread/details/?threadid=dca76bff-cf87-f011-b4cb-0022482e27fc

Configure Session Timeout - Business Central | Microsoft Learn

Was this reply helpful? Yes No
CD-12051622-0 58 on at

Like (2)

Report
Copy link

Link copied!

Thank you everyone for your responses. I’m going to use the retry method.
I would also appreciate any advice or guidance to help me improve my skills on Business Central — I’m open to any recommendations.

Was this reply helpful? Yes No
Suggested answer

AndrewThomas81 2,228 on at

Like (1)

Report
Copy link

Link copied!

Microsoft Learn has plenty of content

There are lots of free training videos on youtube also

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Update:

Business Central known issue: Business Central Task Scheduler and Replication Issues
https://admin.powerplatform.microsoft.com/support/knownissues/6385109

Was this reply helpful? Yes No
Gerardo Rentería Ga... 27,280 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

About inactivity timeouts
Use Job Queues to Schedule Tasks
Get ready to synchronize master data
Analyzing Job Queue Telemetry
Task Scheduler

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,544 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,
What you describe is pretty normal in BC SaaS. If a maintenance window or platform restart interrupts the job queue, the MDM entries can end up suspended and usually they do not restart alone.

We had similar behaviour before and we solved it by increasing the retry attempts and adding a rerun delay on the job queue entries. One thing to note, the entries that are already suspended will stay like this until someone restart them manually, so you need to re-activate them once after you fix the settings.

I would also recommend to use a dedicated service account for the jobs. Technically a normal user account works, but sooner or later password changes or disabled users will cause problems.

Also make sure the jobs are set as recurring so they can queue again automatically after a failure. And monitoring the failed entries helps a lot too.

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards

Gregory Mavrogeorgis

Work: GMSOFT Limited
Blog: Inside Business Central
LinkedIn: www.linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
CD-12051622-0 58 on at

Like (0)

Report
Copy link

Link copied!
Hello,

I am currently working on setting up MDM / Master Data Management synchronization in Business Central between one source company and several subscribed companies.

I will need to integrate a large number of synchronization tables. During my first tests, I encountered many errors such as:

The record already exists on several setup tables;

match-based coupling issues on Customer, Vendor, and Contact tables;

conflicts caused by data already existing in the destination company.

I would like to know the best practices to avoid as many synchronization/integration errors as possible before launching a large-scale synchronization.

For example:

Is it better to use an empty destination company or a pre-configured one?

Should synchronization tables be launched one by one at the beginning?

Should match-based coupling be configured before any synchronization?

What is the best way to handle records that already exist in the destination company?

What settings do you recommend for fields such as validation, overwrite local changes, create if not found, etc.?

Is it recommended to first test with only a few records before synchronizing all tables?

My goal is to secure the integration process and avoid generating thousands of synchronization errors like during my first tests.

Thank you in advance for your advice and feedback.

Was this reply helpful? Yes No