When a user in the client app tries to deploy a sensor, the services first check to see if a sensor with all the matching properties exist already, and if so, it returns the already existing sensor. The next step is a sensor status is created. This issue leads to multiple deployed statuses being created on the same sensor.
Maybe we need to instead of returning an existing sensor, return an error or warning stating that a sensor already exists so that this doesn't happen.
When a user in the client app tries to deploy a sensor, the services first check to see if a sensor with all the matching properties exist already, and if so, it returns the already existing sensor. The next step is a sensor status is created. This issue leads to multiple deployed statuses being created on the same sensor.
Maybe we need to instead of returning an existing sensor, return an error or warning stating that a sensor already exists so that this doesn't happen.