Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Batch job parameters r...
Microsoft Dynamics AX (Archived)

Batch job parameters returning to default settings

(0) ShareShare
ReportReport
Posted on by Rossatron 25

Hi all,

I have a batch job that has been running every night for the past 13 months with the "Last selection" flag ticked and a whole bunch of select criteria. No changes have been made to it in that time, then suddenly last night, for no apparent reason, it ran with the "Last selection" flag unticked and no select criteria other than two default values (sales order status and order line stop).

There is no evidence of anyone tampering with it. Nobody works over the weekend either, so for it to run Saturday night with the criteria then Sunday night without is baffling.

Anecdotally I have since heard that this sort of thing happened a number of times before but affected different batch jobs. Rather annoyingly the support analyst involved at that time just corrected the criteria without investigating root cause and didn't log anywhere which batch jobs were affected how and when.

Has anyone else ever experienced this sort of thing?

If so, double you tee eff is going on?

Thanks.


Ross.

*This post is locked for comments

  • Rossatron Profile Picture
    Rossatron 25 on at
    RE: Batch job parameters returning to default settings

    As far as I can tell nobody has made any changes to it, either to remove it from the queue, change the schedule, modify any parameters or even to stop and start the job. It didn't encounter any errors in the correct run on Saturday evening.

    And as I mentioned it happened over the weekend when nobody was in the office or working remotely. Access to the batch jobs is quite strictly controlled too, so I'd expect anyone with permission to do it would know better than to delete stuff like that.

    It's a puzzler.

    Thanks for your input, Crispin, but I'm starting to think this is one of those things I'm never going to get to the bottom of.

    Fortunately we keep a log of all batch job parameters so we have been able to recover what was lost.

    My advice to anyone would be to keep a log of your batch job parameters, just in case.

  • Rossatron Profile Picture
    Rossatron 25 on at
    RE: Batch job parameters returning to default settings

    Thanks Crispin.

    So are you saying that batch job variables are stored in temp files? That's a bit disaster prone, isn't it?

    If that is the case, why would I only lose the variables for one batch job when we have hundreds?

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans