Finance | Project Operations, Human Resources, ...

Export to BYOD Job (Recurring) Stuck Executing: Is data missing?

(0) Share

Report

Posted on by zachary.robinson@gt...

We have a series of byod export jobs running for a variety of data entities/tables. We have run into this issue before of a a byod export job stuck on executing specific data entities, pausing the entire job.

We are going on a week of two export jobs being stuck on executing, and I am concerned that the incremental refresh will not pick-up all of the records. For example, the last occurrence of a byod export job getting stuck, we had to do a full push of the general ledger table due to vouchers missing during the week that it was stuck on executing.

Has anyone else run into this issue? Can it be resolved on the azure side for the db?

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Alireza Eshaghzadeh 15,140 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi zrobins6,

I have some questions regarding this issue

Does it related to the Production environment?

Which product version does this environment have?

Does it apply to standard entities or just custom ones? can you provide the error message when they stuck on executing?

Do they work with FullPush?

Thanks!

Alireza

Was this reply helpful? Yes No
zachary.robinson@gt... 99 on at

Like (0)

Report
Copy link

Link copied!

Hey Alireza, thank you for responding.

Yes, it is in production environment. It applies to both standard and custom entities. Again, these had been executing before, but got stuck executing while other byod export jobs were running fine. There is not an error message for the job, it just states that it is executing. We are on 10.0.20 (10.0.886.103)

Does this have to do with the azure cpu or capacity being too low, causing the job to get stuck?

Was this reply helpful? Yes No
Suggested answer

Alireza Eshaghzadeh 15,140 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Zrobins6

Thanks for clarification.

There can be several potential root cause for this issue. I have provided the following point that you can try:

-Please check the environment monitoring > SQL insight and Health metric from LCS to get more info regarding the batch AOSes while the export jobs are running to find the potensial root causes.

-You can also evaluate to run "Update statistics" for the affected tables via the LCS This action is performed to improve the query performance of the tables. The statistics can be updated for all the underlying table of the data entity. docs.microsoft.com/.../querycookbook

Query cookbook - Finance & Operations | Dynamics 365 | Microsoft Docs

-Try using Skip staging option on entities and then run the export to BYOD database,

-Try to republish the entity to the Azure SQL DB and then activate the change tracking.

-Check the load in Azure SQL BYOD Database and increase the tier size as needed. If a high volume of records are being exported to BYOD, you can evaluate to use premium service.

-As a suggestion for minimizing batch job contention (including BYOD jobs that running via batch), you can limit the number of exports running in parallel to avoid Batch Jobs issues and activate the feature for "Batch framework contention reduction".

I hope it helps,

Regards,

Alireza

Was this reply helpful? Yes No
Suggested answer

Frank Bruemmer 354 on at

Like (1)

Report
Copy link

Link copied!

This is a known issues we just got resolved by applying the latest quality update : Issue 587953 - Resolved. Check this out : fix.lcs.dynamics.com/.../Details

Was this reply helpful? Yes No