Once the user clicks the Submit button in any tool, immediately disable the button until the job state changes to completed or canceled to prevent repetitive submission of the same or similar jobs by the same user and decreasing the server resources available to other users. This does not pertain to implicitly called jobs, like e.g. source extraction in the WCS Calibration tool with "Show source extraction overlay" enabled.
A determined soul may still submit multiple jobs of the same kind by opening multiple Afterglow windows/tabs, but it at least decreases the temptation to do this on a regular basis.
There is a question: what if a job does not complete at all? However, with the new Celery-based job server, this is unlikely since
the job is killed by the server if it takes too long to complete;
even if the worker is killed, the job is marked as canceled.
Even if the job is left in the pending/in_progress state forever, reloading the page should bring the Submit button back.
(Decision made on the 11/2/2023 meeting)
Once the user clicks the Submit button in any tool, immediately disable the button until the job state changes to completed or canceled to prevent repetitive submission of the same or similar jobs by the same user and decreasing the server resources available to other users. This does not pertain to implicitly called jobs, like e.g. source extraction in the WCS Calibration tool with "Show source extraction overlay" enabled.
A determined soul may still submit multiple jobs of the same kind by opening multiple Afterglow windows/tabs, but it at least decreases the temptation to do this on a regular basis.
There is a question: what if a job does not complete at all? However, with the new Celery-based job server, this is unlikely since