SarcasticSquirrel56 , this can happen. Since you killed the process by force - it didn't have a chance to report back it's failure/stopping.
That being said - there are background processes that should move the dataset to 'aborted/stopped' after a few hours.
Thanks! Not even if using a SIGTERM?
SarcasticSquirrel56 when the process dies (i.e. killed) it does not have time not update the state, then the server watchdog will set the state to aborted after X amount of time of inactivity (default is 2 hours)
Sigint (ctrl c) only
Because flushing state (i.e. sending request) might take time so only when users interactively hit ctrl c we do that. Make sense?
You can definitely configure the watchdog to set the timeout to 15min, it should not have any effect on running processes, they basically ping every 30 sec alive message
but for sigterm you should be able to set cleanup steps, no?