Currently there are two ways an observation to be marked as failed:
- Observation has none of the artifacts(audio, waterfall, data) uploaded.
- Observation has audio artifact with duration at least 1min different from the scheduled duration.
The second case is still under investigation as it happens in several stations, but seems to be affected by different factors (sdr, scripts running before/after the observation, cpu usage etc).
Marking the waterfall with “has signal” changes the observation status. As vetting is in transition, I wouldn’t care too much, if you can keep vetting the waterfalls of your observations then it’s ok, if not then again it’s ok.
Edit: Check also this thread What am I supposed to do with all the unvetted observations?. Unfortunately some other tasks have been prioritized, so discussion on vetting has been stalled, but hopefully it will start again soon, so we can move forward.