Thanks for the quick reply. You bring up some good points.
For this scenario, we "think" we know what caused it and how to prevent it from happening in the future. We re-ran the task/jobs and the execution of the jobs a 2nd time runs successfully. However, this does not remove the historical logs from the provisioning queue.
I like the idea of stopping the dispatchers, taking a copy of the database, and then deleting the records.
Or, we may clean the provisioning queue completely out as part of our support stack installation in a few months. There's about 1,500 entries in the provisoining queue that never go away and have been sitting there for several months.
