...
We had a discussion on how the current Task implementation is not persisted and that this could be problematic during things like reboots. As a client it would be beneficial for ODIM to at least know that a task that use to exist was in flight after a reboot and to display some type of unknown state (maybe 'Interrupted') for the task after a reboot. This again can be treated as a bug fix