Nav2017 JobQueue launch a report execute ok but didnt do nothing

rcseip

Hi,
I have 2 environment of nav 2017, one for development (in our servers) and one for production(in Azure).
I develop a report that check records on a table, if they have Status = Awaiting it grab the record, block warehouse entry and insert the rec in it, go back to the table and change status Awaiting to Inserted.

the funny thing here is that i develop this in Dev environment, the report works and i set the job on queue and check that it works fine, all good since here.
(Dev environment is a copy of Pro with a difference of 2-4 months in data no development in job queue) (User that launch job have "SUPER")

But when i export the objects to pro environment, the report itself works fine but when I add it to the job queue the logs said it execute fine but when i check the status column of the table the record still "Awaiting" then i check warehouse entry and the report didnt do nothing here.

How can it be posible that it execute ok with dev environment, a copy of pro environment, but when i import to pro it fails.... and the logs said it work.
To fix this temporary i set a page with a PageAction to launch the report, but ill apreciate if i can fix the queue problem and make it to launch automatically.

I have other jobs in the queue that works fine.

Anyone can let me a hand, please?

rcseip

i think i choose the incorrect category for the post, maybe should be in "Nav Three Tier" any admin can move this to the right category?

Sean56

It sounds like your report works manually but fails silently in the Job Queue on Prod. This is often due to how NAV 2017 handles Job Queue sessions — even with "SUPER" permissions, background jobs can behave differently.

Possible Causes:
Missing explicit permissions in the report or codeunit

COMMITs or error handling not behaving the same in background

Data differences causing a specific record to fail silently

Job Queue session skips some triggers/UI logic

Fix:
Try running the report manually in Prod as the Job Queue user.

Add logging or error handling in the report to catch silent failures.

Consider moving logic to a Codeunit and calling that from the Job Queue.

Let me know if you want help