Hello,
I am trying to troubleshoot a long-running scheduled job for the Cost Adjustment Report, but I am unable to find any resources on how to actually see what is going on behind the scene. Is there any option to view the current row/task that the report is working on? How to troubleshoot this kind of task?
Thank you! Cheers!
Once the item is known try running the adjust cost item entries routine for that one item in the regular UI. If you hit a lag like the job queue then use the debugger and set a break point early on in the report. Be a case of stepping through until you hit something which seems odd
Hello,
Josh's direction is correct. I would say try filtering Items, from the Adjust Cost - Item Entries routine, that have recently been transacted against and Cost Adjusted = FALSE. This will help narrow the Item that needs addressing.
Steve
Hi Josh,
I found one article the keeps repeating in the Profiler, what should be my next step?
Thanks,
Milos
Thank you for the suggestions! The big mystery here is that everything was fine a few days ago, the job took 15 minutes to finish, and now it just won't complete. I will try the options mentioned and hopefully get on top of this. Happy New Year!
Debugging won’t help here as it is based on reviewing when a line of code is called. You can set filters but you don’t have that info in this instance. SQL level tracing might be more suitable here. Check out how to setup a SQL profiler: docs.microsoft.com/.../sql-server-profiler
This seems like a steady standard option. Another possibility using modification would be have a event subscriber log the item number in a bespoke table so you can see where it has got to or which record it’s working on. That way you can compare the bespoke log to the job queue log entry to understand which record is taking so long to work on.
Longer shot would be to look on the item table at which items need adjusting. “cost adjusted” will be false. Then check out the value entry table and see which of the first list of items appears the most. More than likely it is that one the report is hanging on but this is less definitive than the other things I mentioned. Might help provide a few choices for a filter when debugging though.
Sohail Ahmed
815
YUN ZHU
773
Super User 2025 Season 1
Mansi Soni
569