Current implementation allows user to edit a record to change from managed data to externally published HTTP data; however, no consideration is given to running tasks that may be accessing the associated raw data, owner, or allocation. Publishing data is a destructive event and must fully isolated from other running tasks. Existing and subsequent read tasks may fail by not seeing the correct data location, so publishing data should be treated like a "delete" operation - i.e. not allowed to run concurrently with any other tasks, and should be handled immediately, rather than as a background task (file delete task would still be created).
Current implementation allows user to edit a record to change from managed data to externally published HTTP data; however, no consideration is given to running tasks that may be accessing the associated raw data, owner, or allocation. Publishing data is a destructive event and must fully isolated from other running tasks. Existing and subsequent read tasks may fail by not seeing the correct data location, so publishing data should be treated like a "delete" operation - i.e. not allowed to run concurrently with any other tasks, and should be handled immediately, rather than as a background task (file delete task would still be created).