I have just posted 2 suggestions on Microsoft Connect about the Job Queue.
Extra votes, if you agree, will certainly help getting the attention for it.
Issue 1: Job Queue Stability:
The new Job Queue start background sessions for each job queue in each company. That Job Queue updates his heart beat to the Job Queue table. However, sometimes, if the background session stops working, the Job Queue table doesn’t receive a heartbeat and is still marked as started.
The Job Queue main process should check these heartbeats and take action.
Issue 2: Job Queue Entry User ID
However creates the Job Queue is set as the User ID for that entry. Which means that any error gets sent to his notifications (so far, no problem).
The Job Queue Entry is actually always executed as the service account, BUT before starting the entry, there is a check if a user has permissions to run the entry object.
We have some functionality, which creates job queue entries on the first run, meaning the first user to log in is the “User ID” for this entry.
Image this: as an IT Manager, I create an entry to import EDI entries.
A few years later I quit my job, of course, my account is blocked and removed from NAV. This means the job queue will no longer run, since the user does not have permissions…
Guess where the notifications are sent? Right, to my notification Factbox on my role center, which I don’t check, since I quit my job 🙂
So, as long as no one reports that they aren’t sending out orders or receiving orders, EDI will no longer be ran.