If a sensor was simply removed by SQL, the cleanup we put in place would not have happened (it happens on deletion via the code).
How can we make the flx-config and graph dialogues robust against sensors (and assets) which are missing, even though our config still refers to them?
If a sensor was simply removed by SQL, the cleanup we put in place would not have happened (it happens on deletion via the code).
How can we make the flx-config and graph dialogues robust against sensors (and assets) which are missing, even though our config still refers to them?