The Argo bulk action republish feature starts uses the default publish queue. When running a large bulk action republish, this can result in a large backlog of queued jobs that also slows down accessioning because they share the same queue for the "publish" step in accessioning.
If we can put the bulk action republishes in the "low" queue, then they should not interfere with accessioning. Accessioning tends to be sporadic so there should be plenty of time for items in the low queue to catch up when there is little accessioning activity. It's ok if bulk action republishes take a bit longer this way.
Additional context
I occasionally start large bulk action republishes after hours in order to avoid interfering with accessioning. So I, personally, would benefit from being able to run them during business hours. Examples of where a bulk action republish is needed:
republishing purls after cocina has changed
certain types of remediation, usually related to problems with releasing items to SW
The Argo bulk action republish feature starts uses the default publish queue. When running a large bulk action republish, this can result in a large backlog of queued jobs that also slows down accessioning because they share the same queue for the "publish" step in accessioning.
If we can put the bulk action republishes in the "low" queue, then they should not interfere with accessioning. Accessioning tends to be sporadic so there should be plenty of time for items in the low queue to catch up when there is little accessioning activity. It's ok if bulk action republishes take a bit longer this way.
Additional context
I occasionally start large bulk action republishes after hours in order to avoid interfering with accessioning. So I, personally, would benefit from being able to run them during business hours. Examples of where a bulk action republish is needed: