This isn't (at least at first) Pause/Resume as you might be expecting - where
you could manually pause a currently running job and continue it later. What
we're doing at least in the first pass is using 'Paused' as an internal state
that jobs only go into in two scenarios:
1) User quota is
Thanks Dannon.
No worries. Yes my interest was different. On a private local Galaxy, or a
private Cloud one, sometimes a job seems to be going awry, taking forever
etc. I was interested in the ability to suspend it, check what's wrong,
maybe fix it, maybe resume or cancel the job.
Rgds,
Greg E.
