Sometimes there are too many tasks running because i.e. the render job is set to run immediatly once a document is added to the publisher queue. This may end up having 100+ instances of the ESPADM64.exe running and waiting for a previous task to complete. This process, in my experience, get stuck after some time.

You really want a cancel all option here, else you have to stop all instances manually. You have to select each running task one by one to cancel them. That is alot of clicking to do.

Or perhaps instead of a cancel all/restart all make it possible to select multiple running jobs and cancel/restart those with one click.

Thank you again for your suggestion.

There are considerable risks when acting on the entire queue. For example, other users may have added items that are not part of the intended mass changes, either through a workflow process or a manual request. The mass change would then impact these queued items unintentionally.

An alternative would be to introduce the ability to filter on the queue, then execute bulk change.

Would this flow of first filtering on the queue and then applying a change to the filtered set, work for your situation?

Chris Tsangarides
Product Manager
Accruent

Thank you for your suggestion.
Development is currently reviewing your idea and is being considered for a future release. Stay tuned for updates.

Chris Tsangarides
Product Manager
Accruent

Any comments on this? It should be fairly simple to implement.

Legacy ID: MER-I-102

Idea created at: 2018-Jun-28

Referenced customer:

COMMENTS: