Regarding Observation 13350157 …
This obs was marked as failed and I’m not sure what triggered it. I don’t recall when an observation gets marked (after X minutes and no waterfall, but the client takes a little longer to finish post-observation tasks?)
Knowing will help troubleshoot the issue.
Both of our active stations are sorely due for the client upgrade, which will be the first step and perhaps clear up the auto-tagged failures.
Your timeframe shows about 460 seconds but the waterfall only shows about 330 second. So the observation failed because of (a lot of) dropped samples.
Ouch, 30% dropped samples is … not good.
Thanks for the help!
Just to add that actually the check is with the audio duration vs the observation duration. If the difference is more than 1min then the observation is marked as failed and need to be checked.
Usually this happens due to cpu move to lower clock speed (less Hz) which can be caused due to faulty power supply or high temperature.