Thanks for the steps to reproduce, I think I was also using the "record" button on the OSD rather than the EPG. I can repro the problem so I will debug it if krusty doesnt beat me to it
From the log file, the front end sends through "the brady bunch" (dont ask) as the name of the show to record, but the backend replies with "Old School Neighbours" which is the show afterwards.
2013/09/18 09:14:38.088 Received client request: scarecrow|SetTimer|-1|11054|0|1379466878|0|The Brady Bunch|50|0|10|0|3629|0
2013/09/18 09:14:38.412 SE: 17/09/2013 11:30:01 PM - 18/09/2013 12:00:01 AM on ELEVEN -> Old School Neighbours - Id:0xE000000018C82 (3940649674050690)
2013/09/18 09:14:38.436 assignment: 17/09/2013 11:30:01 PM-18/09/2013 12:00:01 AM on 11 : ELEVEN - 2B2E = { (11 : ELEVEN - 2B18) + [ 11 : ELEVEN - 2B3C, 11 : ELEVEN - 2B55] }(Device: Digital Antenna (DVB-T) - 1AA : 2b1791e7-37ab-4b47-8eb0-91824020e787 - 2988 TuningSpace: DVB-T - 2B56)
2013/09/18 09:14:38.495 SetTimer> recording scheduled for The Brady Bunch on channel 11 : ELEVEN - 2B2E = { (11 : ELEVEN - 2B18) + [ 11 : ELEVEN - 2B3C, 11 : ELEVEN - 2B55] }, RecordingState: WillRecord
It seems the way instant records works is kinda funny
![Smile Smile](https://forum.kodi.tv/images/smilies/smile.png)
XBMC sends in 1/1/1970 as the start time and NOW as the end time. The backend code detects this and corrects it to a start time of NOW and then looks for program entries in the EPG from now to now+8 hours with a comment that it should be a big enough period to find an entry. But it seems this query isnt returning the current show, in my case it returns 34 entries but the first entry is the following show. It shouldnt be too hard to correctly identify the in progress show