Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Release 10.0.39 Batch ...
Finance | Project Operations, Human Resources, ...
Unanswered

Release 10.0.39 Batch job history changes

(3) ShareShare
ReportReport
Posted on by Community member 10
Hi Experts,

Need help to understand and mitigate the new changes related to batch jobs in 10.0.39 release. We don't want to loose any of the job history.

Feature from Release Note:
If the batch job has more than 5,000 batch tasks, then the corresponding job history would only save first 2,500 tasks, preferring tasks with status in following order: Error -> Canceled -> Finished -> Not Run. This measure has been implemented to prevent blocking batch related tables that may occur due to such large jobs. For more information, see Create a batch job.
  • Community member Profile Picture
    Community member 2 on at
    Release 10.0.39 Batch job history changes
    In the 10.0.39 release, a significant change has been made regarding batch jobs, particularly regarding how job history is handled for large batch jobs with more than 5,000 batch tasks. Previously, all batch tasks were stored in the job history, regardless of the job size. However, to address potential performance issues and prevent blocking of batch-related tables due to the size of such jobs, a new approach has been implemented.
    Now, if a batch job contains more than 5,000 tasks, only the first 2,500 tasks will be saved in the job history. However, it's crucial to note that the system prioritizes which tasks to save based on their status. Tasks with the status of Error, Canceled, Finished, and Not Run will be saved first, in that order of priority.
    To ensure that you don't lose any critical job history data, it's essential to understand this new behavior and take proactive steps to mitigate any potential impact. One approach could be to regularly monitor and archive job history data for large batch jobs, especially those exceeding the 5,000-task threshold. By periodically archiving historical data, you can maintain a comprehensive record of job history while also managing database performance effectively.
    Additionally, consider optimizing batch job configurations to minimize the number of tasks generated for large jobs wherever possible. This could involve breaking down large jobs into smaller, more manageable batches or optimizing job scheduling to distribute workload more evenly over time.
    Overall, by staying informed about these changes and implementing proactive measures to manage batch job history effectively, you can ensure that your organization continues to benefit from efficient batch processing without sacrificing critical historical data.
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,642 Super User 2024 Season 2 on at
    Release 10.0.39 Batch job history changes
    Hi,
     
    This message is about tasks within a batch job. I haven't seen this number of tasks used apart from one scenario where someone added a task per record using X++ coding instead of a bundle of records.
     
    Do you have batch jobs with this huge number of tasks? 

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.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,642 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,371 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans