id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
13094	Dvr/GetUpcomingList?Count=1 is reporting an old scheduled recording after a recording failure	stephen@…	Bill Meek	"MythTV Version : v0.28.1-38-geef6a48
MythTV Branch : fixes/0.28
Network Protocol : 88
Library API : 0.28.20161120-1
QT Version : 5.5.1
Options compiled in:
 linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr using_xv using_profiletype using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2

I had a recording failure for a recording using minisatip (IPTV) for Midsomer Murders.  The recording never started due to a problem in minisatip.  When I eventually noticed it, I manually stopped the recording.  Then, when I called the Dvr/GetUpcomingList?Count=1 API, I was getting back a result saying that the Midsomer Murders recording scheduled for 2017-08-08T00:45:00Z is the next recording to happen (see GetUpcomingList.xml file).  That start time was in the past, but the end time for that failed recording (2017-08-08T02:25:00Z) was still in the future.  I tried restarting mythbackend, but that did not change anything.  I then waited until after that end time, and the API call then correctly returned the next scheduled recording."	Bug Report - General	closed	minor	needs_triage	MythTV - Services API - Backend	0.28.1	low	Trac EOL	API GetUpcomingList		0