Closing rollback failure dialog permanently blocks future rollbacks

[grantfitzsimmons]

Describe the bug
If you attempt to roll back a data set which has a blocking record, then refresh the page before clicking the "Stop" button in the dialog with the error, you are permanently locked out from attempting this action again due to the uploaderstatus caching the state.

To Reproduce
Steps to reproduce the behavior:

1. Create a new record in a WorkBench upload

   

2. Create a new record in data entry (or WorkBench) and link it to that record (e.g. a new agent in a new CO)

   

3. Attempt to rollback the new upload and notice that there is an error shown

   {
     "uploaderstatus": {
       "operation": "unuploading",
       "taskid": "5e770147-5027-43e5-80e9-08e83e0b22c5"
     },
     "taskstatus": "FAILURE",
     "taskinfo": "RollbackFailure('Unable to roll back Agent object (2571) because it is now referenced by another record.')"
   }

   

4. Close the tab without clicking on the "Stop" button in the error dialog

5. Navigate back to the WorkBench data set

6. Click Roll Back and confirm the roll back initiation

7. See that it returns you to the data set without any warnings in the UI

8. Check the 'network' logs, or the console, and see the error:

{
    "type": "invalidResponseCode",
    "statusText": [
        "Invalid response code 409.",
        "\n    This error happened because the resource you tried to update has already\n    been modified by someone else. Please refresh the page and try again.\n  ",
        "Response:"
    ],
    "responseText": "dataset in use by uploader."
}

This leaves the user in a position where they cannot roll back the data set even if they removed the link. To proceed, they need to clear the uploaderstatus value for that record in the spdataset table manually, which cannot be done using the UI. Here's an example of what gets stuck in the uploaderstatus column:

{"operation": "unuploading", "taskid": "bb5bf16c-1293-4c60-b347-29ad76af2076"}

Expected behavior
If the dataset in use by uploader. message is being received, the user should see it in the UI. The user should have the ability to stop the process and have it function just like it was cancelled rather than making the option completely inaccessible if they did not click the "Stop" button before the tab closed.

Screenshots
If applicable, add screenshots to help explain your problem.

Crash Report
Occurrs on v7.12.0.6 and main (7fc918f).

Arc browser, macOS, recreated on https://sp7demofish.specifycloud.org/

[grantfitzsimmons]

Encountered by Lucas on NMB-FVERT today: https://specifysoftware.bolddesk.com/agent/tickets/1101, but in this case it wasn't due to a referenced record, but just due to a stale uploaderstatus