Notifications
Announcements
No record found.
Hello,
We have approx. 8 batch jobs running every 20 mins during business hours, plus other overnight jobs in Dynamic 365 Finance and Operation. The jobs are for system integration, which pulls and pushes data between 2 systems. There could be a lot of data. Will that cause any performance issue during business hours? Or is there any guideline and what is the best practice?
Your help is greatly appreciated! Thanks!
You may use priority based batch scheduling.
docs.microsoft.com/.../priority-based-batch-scheduling
whenever possible, it is recommended to schedule jobs that may affect performance outside of working hours.
if you register, millions of transactions during business hours, users might be affected. But every process is different, I would recommend monitoring the processes and analyzing if they affect the performance of the D365.
I understand it is the best if we could schedule the jobs after hours, however, due to business needs, we have to sync both systems consistently in order to get the live data. I wonder what would be the reasonable settings in order meet the business needs and maintaining a good performance.
Thanks in advance.
Hi Wandal,
Like Nuno mentioned, you should monitor the performance. Probably, you can setup a test environment for some simulations to change the frequency. We don't know what exactly is part of the integration and how many records are involved. Is it reading data only or also inserting or updating records in F&O? That would make a difference.
I will provide you an example which illustrates that the way how the system is used and number of transactions might have an performance issue which was solved in a certain way with a small customization:
In the past, I had seen an enormous performance issue with the workflow execution. This used to run once a minute and should run once a minute. Due to some unusual workflow configuration, instead of easily handle e.g. 600 workflows in a minute, it took for some workflows 1 complete minute, having 99 in the queue which also took in total almost one hour. This was unacceptable for the timesheet and project invoice proposal workflows. As we were not able to change the workflow configuration, we decided to split the workflow tasks per workflow type. In that case, we solved the performance issue for the business critical workflows.
Thanks Andre. That's very help. Our integration is bi-directional. So, it involves reading and updating the records in F&O.
In your example, you mentioned splitting the workflow tasks per workflow type.
Do you mean:
1. Setting the scheduling priority (Low, Normal, High, Critical...) or
2. Having a smaller set of data in your workflow or
3. Scheduling them out of business hours for some of workflow?
Thanks in advance!
It depends on what is your urgency to get the data. I would offer you to first smaller sets while if one batch is not finished other do not start. Second to have prioritize. Spare the Aos for batches.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 663 Most Valuable Professional
André Arnaud de Cal... 540 Super User 2025 Season 2
Sohaib Cheema 348 User Group Leader
