Feature Request: Advanced Multi-Row Queue “Abort” Row

[mkreitzer]

This would be similar in idea to the special execution row. An “abort” row would be a special row in the queue that only gets executed if the “Abort advanced multi row sequence” command is used in any rows execution.

This would allow a generalized cleanup and alerting row to be optionally executed in cases where an abort is required.

[doug]

I’m a bit confused on this one.

What advantage would this provide over just adding the desired alerting/cleanup to a particular job queue where you are using ‘Abort advanced multi-row sequence’ in your queue? Why would you want/need a generalized row for this purpose when you can build anything directly into a given job queue?

Are you talking about manually executing ‘Actions > Job queue > Abort’ as opposed to having it execute within a job queue step? If you’re manually executing it, why would you then need an auto-trigger for some other cleanup? At that point wouldn’t you just manually execute whatever cleanup stuff you want since you manually performed the abort command?

[mkreitzer]

Mostly as a DRY utility, and also for maintaining manageability over large sets. These queues get a little unwieldly when you start pushing 60+ actions. Think of it as something similar to a try / catch block. The “try { }” is all the ordered indexed rows. The “catch { }” is the special abort row I am requesting, and the “throw()” is “Abort advanced multi row sequence”.

I can put all error handling logic for a grid in one place, rather than scattered around. It also helps in my efforts to minimize the number of unique job queues which has benefits for maintenance and legibility.

[Author]

Posts