Steps to reproduce:
1. Schedule a capture which will fail (for instance, a one-minute-long capture which starts less than a minute after another capture finishes --the capture agent delays the starting time one minute, so the capture remains with a 0 minutes length, and it's skipped – this behaviour could be a bug by itself).
A RecordingImpl object is never created (the recording is simply skipped). Therefore, nobody will ever notify that recording's state and the core "guesses" that it failed because it does not report to be "capturing" when it's suppossed to. However, even though the recording is shown as "failed", it appears under the "Upcoming" tab