What happens when I Run Workbook on a workbook that already has a job running?

I'm just a "user" of our Datameer environment; I have zero administrative privileges. Our administrative team for Datameer has made it VERY clear that we are NOT to cancel any jobs. Apparently it causes major problems in the environment that impacts all users / customers.

I have a workbook that I made some adjustments to, saved, and ran. So the job is out there running and seems to be taking a long time to finish. It's sat at 83% for hours now. I want to go in and change some things to hopefully optimize the workbook.

So what happens if I go in, edit the workbook while it's running, save it, and run it again? Will it cancel the currently running job? Will it queue up another job to run after the current job finishes? Will it fire up another job independent of the existing one?

I really don't want it to 'cancel' the job and thus get me in trouble for canceling a job. They will actually take away my access if I cancel a job!

Please advise; thanks!

Joel Stewart

August 29, 2016 22:13

I reproduced this scenario in my environment and found that if a Workbook is in a Queued or Running status, when I save a workbook and elect to start it immediately no additional execution of the job is queued.

The edited workbook job will only queue if elected and if it is not already queued or running.

MorganM

August 30, 2016 14:14

Thanks Joel! I really needed to know and couldn't test myself or risk loosing my login =/

Apparently if we cancel a job the hangs the queue for the entire environment. That's why they are taking such a hard line on offenders.

What happens when I Run Workbook on a workbook that already has a job running?

Comments

Didn't find what you were looking for?