What steps will reproduce the problem? 1. Not sure what the 100% reproducible case is, but this happened for all 4 NFL playoff games this weekend (and I've seen it happen once or twice in the past couple of weeks as well) 2. Began watching NFL playoff game live 3. Noticed that the NFL game was flagged as a manual recording (but not by me) 4. At the end of the game, I could not cancel the recording. I tried removing the manual flag several times to stop the recording, but SRE kept putting it back on.

What is the expected output? What do you see instead? Expected SRE to not monitor or extend the recording. Instead, SRE monitored the recording and extended it to the default 4 hours. Once in this state, I could not cancel the recording until the 4 hours had past.

What version of the product are you using? On what operating system? Latest. Windows XP.

Please provide any additional information below.

Here is the entry in the log from the start NYG/ATL game today. Seems like because the teams were unrecognized, the default padding kicked in even though the game should not have been monitored:

2012-01-08 12:58:29,862 INFO : 18457164/FOX NFL Sunday: Monitor disabled because it is an unmonitored event. 2012-01-08 13:00:00,596 WARN : 18457104/NFL Football: Error from web service; applied default padding. 2012-01-08 13:02:00,252 WARN : 18457104/NFL Football: Error from web service; safety measures already applied. 2012-01-08 13:04:00,299 WARN : 18457104/NFL Football: Error from web service; safety measures already applied. 2012-01-08 13:06:00,221 WARN : 18457104/NFL Football: Error from web service; safety measures already applied.

And every time I tried to manually stop the recording, SRE kicked back in with a message like this: 2012-01-08 16:50:11,940 WARN : 18457104/NFL Football: Error from web service; applied default padding. 2012-01-08 16:50:12,393 WARN : 18457104/NFL Football: Error from web service; applied default padding.

What was the episode name for the airing(s)? Was it like "Teams TBA" or something like that?

This report brought about two separate bugs; issue 332 and issue 333 opened for the separate issues. Marking this issue as a duplicate of 333; I've CC'd you on those two issue tickets instead; unstar them if you don't want the notifications.