Discussions
Activity
Best Of...
Sign In
·
Register
Home
›
NAV Three Tier
Howdy, Stranger!
It looks like you're new here. Sign in or register to get started.
Sign In
Register
Quick Links
Categories
Recent Discussions
Activity
Best Of...
Unanswered
Categories
All Categories
73
General
73
Announcements
66.6K
Microsoft Dynamics NAV
18.7K
NAV Three Tier
38.4K
NAV/Navision Classic Client
3.6K
Navision Attain
2.4K
Navision Financials
115
Navision DOS
854
Navision e-Commerce
1K
NAV Tips & Tricks
772
NAV Dutch speaking only
615
NAV Courses, Exams & Certification
2K
Microsoft Dynamics-Other
1.5K
Dynamics AX
308
Dynamics CRM
109
Dynamics GP
10
Dynamics SL
1.5K
Other
993
SQL General
384
SQL Performance
34
SQL Tips & Tricks
34
Design Patterns (General & Best Practices)
Architectural Patterns
10
Design Patterns
5
Implementation Patterns
53
3rd Party Products, Services & Events
1.7K
General
1.1K
General Chat
1.6K
Website
79
Testing
1.2K
Download section
23
How Tos section
260
Feedback
12
NAV TechDays 2013 Sessions
13
NAV TechDays 2012 Sessions
NAV2018 Job Queue not retry after hit error
Panha
Member
Posts:
3
2020-04-24
in
NAV Three Tier
In Nav 2018, i have a job queue that fail sometimes
The error is ok (it's because of some lockted table), so i want the job queue to retry
0
Answers
einsTeIn.NET
Member
Posts:
1,050
2020-05-21
I think this is by design. If you want to restart it automatically you have to implement another solution.
"Money is likewise the greatest chance and the greatest scourge of mankind."
0
kylehardin
Member
Posts:
257
2020-05-22
You have to change the code. Codeunit 448 Job Queue Dispatcher, function GetNextRequest. Something like this:
//JobQueueEntry.SETRANGE(Status,JobQueueEntry.Status::Ready);
JobQueueEntry.SETFILTER(Status, 'Ready|Error');
That is from 2016, so 2018 may have an event you can subscribe to rather than modifying the base object.
Kyle Hardin - ArcherPoint
0
Sign In
or
Register
to comment.
Answers
//JobQueueEntry.SETRANGE(Status,JobQueueEntry.Status::Ready);
JobQueueEntry.SETFILTER(Status, 'Ready|Error');
That is from 2016, so 2018 may have an event you can subscribe to rather than modifying the base object.