The History tab displays the geoprocessing queue but doesn't allow for any kind of on-the-fly reordering. Desired actions include:
*Drag and drop jobs - Bump up a job in the queue priority to finish it quicker or send something to the back of the line
*Pause job - When you don't want to cancel it entirely
*Run now - Pause current job to immediately process a high-priority task
*Schedule job - Create a job and set it to run at a later time
"*Pause job - When you don't want to cancel it entirely" - This part of the request should be diverted over to Include Pause Option in every Geoprocessing Tool where you can add your vote and your use case as a comment if you'd like. I think that if Pause were implemented, you would get this functionality "*Run now - Pause current job to immediately process a high-priority task".
"*Schedule job - Create a job and set it to run at a later time" is kind of likeModel Builder/ Tool Scheduler and Notification. Anyway, scheduling a job will be possible in ArcGIS Pro 2.5 which we have scheduled for January.
Here is a sneak preview:
So the present idea becomes about "*Drag and drop jobs - Bump up a job in the queue priority to finish it quicker or send something to the back of the line" Could you maybe update the idea's title to be more specific about re-ordering jobs in the geoprocessing queue?
How many geoprocessing tools are you typically lining up, can you provide some examples of the typical tools that you put in the queue, and how long might a process run? What would cause you to need to stop a process and immediately run another tool? Could that be accomplished in another instance of Pro? Thanks for any additional details that you can provide.
The idea came up while loading ~10 lidar datasets from a clearinghouse into a GDB. While downloading I would queue up the creation of mosaic datasets then after TIFs were extracted queue mosaic and calculate statistics jobs. Since downloads vary by size a dataset of higher interest would be stuck behind others in the queue.
This would be great functionality to have. When you've got a calculate (or index creation or field add) job running on a large dataset and have a quick task that you want to run so that you can move on to other things, being able to pause the long running job and/or re-order tasks in the queue would be super helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.