Jobs UI: Prevent rapid "double-submit" errors

[rtapella]

• there's a notification when you submit a job, which is good

• you can easily submit the same job twice by pushing the Submit button twice

• if you're running a large job (or a batch) this could cause you to "spend a lot of money" by accident

• prevent the same job from being submitted twice within some time period, e.g. within 5 seconds. This will prevent accidentally double-press errors that trigger the same thing rapidly in succession by accident

[grallewellyn]

Or once the user presses the submit job button, we could disable the submit job button until the job has been successfully submitted? Because I think this problem is arising from the fact that there is a delay between clicking the submit job button to the notification for job being submitted

[rtapella]

Yep that's a good solution.

[grallewellyn]

Discussed in spring planning 10/26
We want to still keep button disabling (I basically have this working), but we want a way for the user to be able to tell that it was submitted if they blinked when the button was disabled and missed the toast notification because large monitor. Potential solutions to this

• submit button changes to resubmit if they already submitted. Downside to this is that you have to keep track of changes in the state of what is in the Submit Algorithm Form
• A little text below the submit button saying that the job was submitted and giving the job ID. How long should this stay up?

[rtapella]

I think a permanent message below the submit button would be fine. It can be the same content as the notification toast.

Like
1.
Submitting job...

2a. Change the content to:
October 23 at 13:45 PST
Job submitted successfully with ID blah-blah-blah-blah

(That will link to the View tab and ideally highlight the job you just submitted)

2b. If failed, change content to:
Job submission failed:
[error message]

If another job is run with the same form, wipe the content of this div and go to 1 (submitting job....)

[grallewellyn]

Sounds good to me

[rtapella]

Jobs submit very quickly. Can we add a minimum disable-time to this? Maybe the "submitting job" can be at least 2 seconds long, and more if the submission is taking a while for some reason.

[grallewellyn]

We could and that wouldn't be a difficult change, but then wouldn't that make our system seem slow if we are purposely delaying things and the job had actually submitted? Is the popup notification and the text underneath not enough feedback for the user for them to know their job was submitted and they shouldn't try to submit it again?

[rtapella]

Sometimes it’s good to delay things to help someone understand what’s happening. In this case there’s no reason to click submit repeatedly, and changing an input to submit a similar job a few times is going to take more than 2 seconds. I don’t think it’ll make the system feel slower in any way that matters here.

I noticed that the “submitting” message flipped by so quickly that I didn’t have time to read it. And I was still able to just keep clicking submit quickly to make a bunch of cloned jobs. So my “concern” is that it won’t be enough to prevent the mistake.

We could just leave it and test it, as well.