We have spotted the issue… is on the db site. It has to do with the recent commit of filtering transmitter by uuid. It is fixed and it’s going to be deployed in the next minutes.
I have removed all the observations (349) in network that were affected by this issue. I’ll let you know here when db changes are deployed so you can starting scheduling again. Until then please avoid to schedule new observations.