web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / batch task failed: max...
Finance | Project Operations, Human Resources, ...
Suggested Answer

batch task failed: maximum retry count (99) exceeded

(0) ShareShare
ReportReport
Posted on by amigup2020 35

We had developed custom batch job to post project adjustment. It was running absolutely file on our previous version which was 10.0.6. last month we upgraded to 10.0.14 and since then the batch job throws error leaving log "batch task failed: maximum retry count (99) exceeded".

When we run the batch job from front end without marking it as batch job it runs fine

Only in batch job mode it throws error in executing in all legal entities.

Any suggestion would be of great help.

Thanks & Regards,

Amit Ashok Gupta.

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,025 Super User 2025 Season 2 on at

    Hi Amit,

    Does the batch history shows some additional error details? Can you also tell what this batch job is about? Probably you can share some details?

  • amigup2020 Profile Picture
    amigup2020 35 on at

    Hi Andre,

    This batch job is basically an automation for Project adjustment which is available through front end in D365 F&O.

    When we check its batch job history it was execution without any error till we upgraded to version 10.0.14. Since then every ten minutes recurrence interval that it executes it throws error for exceeding maximum retry count (99). That's only error we see in every error log.

    Not sure why after version upgrade it started running into error.

    Please do let me know if you require some more detailed information about classes that this batch job is using to post adjustment entries.

    Thanks & Regards,

    Amit Ashok Gupta.

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,025 Super User 2025 Season 2 on at

    Hi Amit,

    Is the automation part of a customization? If so, try to contact the developer for some more help.

  • amigup2020 Profile Picture
    amigup2020 35 on at

    Hi Andre,

    The customization was developed by other vendors. Basically in so many days analysis I feel the batch job suffers from optimization issue.

    To test it I applied date range on createdDateTime field on ProjItemTrans table from which it picks master data and picked records for adjustment for only a month and I didn't got this error at batch job.

    Its only when the batch job picks records from beginning date till date batch job is unable to fetch records. May be after upgrade of .Net framework from 4.5 to 4.6.1 Microsoft has become strict at amount of time a query could hold lock at a table in D365 finops.

    To sum it up I believe I have to optimize the code to pick more recent records rather than picking everything starting from date customer went live with the application.

    I am still keeping this thread active as we might get some insight by others who might have faced similar issue.

    Thanks & Regards,

    Amit Ashok Gupta.

  • Suggested answer
    Sandeep Chaudhury Profile Picture
    Sandeep Chaudhury 3,303 on at

    Hey Amit, Starting version 10.0.11/10.0.12, Microsoft has now provided batch processing of adjustments posting out of the box. Unless you have very custom logic for the adjustment posting for some reason, you should consider removing your customization and take advantage of the standard batch posting.

  • amigup2020 Profile Picture
    amigup2020 35 on at

    Hi Sandeep,

    Thanks for providing us with the info that Project adjustment posting is available out of the box. Though the client business requirement is very complex I will check out the code for the standard batch job.

    For time being I found out that the custom batch job was not optimized well. Seems after upgrade of .Net framework 4.6.1 MS has made process management more rigid which resulted the batch job running of time out to consume resources.

    At present I had applied date range on created date time of ProjItemTrans table to run batch job to pick data at Quarterly basis that resolved this issue for me. Still I would like to find out root cause for this error. As its custom batch job MS won't provide resolution. May be someday I get to know root cause behind this issue.

    Thanks & Regards,

    Amit Ashok Gupta.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 611 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 529 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 285 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans