User bio
404 bio not found
Member since Nov 9, 2015
Posts:
Replies:
This is correct. Once we start a worker job we keep it around for the next time we need a worker job to avoid the overhead of starting a new process. The workers should not be using any significant memory or CPU and will time out automatically after a while so you can leave them alone.
That is correct, however it is far simpler if you use the debugger built into VS Code as this uses our maps from class to INT code to automatically set the correct breakpoint based on the source class line.
Certifications & Credly badges:
Mark has no Certifications & Credly badges yet.
Global Masters badges:
Mark has no Global Masters badges yet.
Followers:
Following:
Mark has not followed anybody yet.
Normally it is required that you call the Sync/WaitForCompelete method on the work queue object so that the module can report errors and you can introduce a sync point where you know that the work done by the worker tasks has completed.
If you do not call Sync/WaitForComplete then what is likely happening if your work queue oref is going out of scope at the end of your procedure which closes the oref and this terminates all work units in this work queue group so if they have not completed at this point they will never get run as the entire queue is removed.