Recordings getting scheduled by deleted timer rule

Sam Malcom

I've noticed that recordings keep getting scheduled by a timer rule which was deleted a while ago. I can tell this by looking at the comment which mentions the timer rule.

I have double checked the timer rule, it definitely seems to be deleted, and no matter what I do the recordings keep getting rescheduled once deleted.

Any idea how I can stop this from happening?

DeltaMikeCharlie

There are 2 similar but different ways to automatically schedule recordings:

AutoRec - Basically key word searches.
Timers - Regular periodic recordings at the same time on the same channel.

Are you able to tell which one of these methods is being used?

Also:
What version of TVH are you using?
How did you originally create the timer rule?
Did you use the TVH WebUI or did you use something like Kodi?

Sam Malcom

DeltaMikeCharlie
Looking at the comment it leaves on the scheduled recordings, it appears to be an AutoRec.
As the timer was created a few months ago, I'm struggling to remember whether it was Kodi or the TVH WebUI. It's quite possible I set it up on one, removed it, and recreated it using another method.

What I have done, is check the Kodi client as well as the web interface to make sure the rule has been deleted on there, and I definitely can't see it listed so believe it has been.

The version I'm using is 4.3-2209_gb225e4d6c

DeltaMikeCharlie

If you can’t see the AutoRec on the TVH WebUI or within Kodi, yet it still creates a recording, then this seems very odd indeed.

If you have more than 50 AutoRecs, you will need to go to the next page or change your ‘Per Page’ option to ‘All’.

It may also seem a bit clichéd, but have you tried rebooting TVH?

You can try 2 other steps:

1) Check your recording to determine which AutoRec the recording is attached to.

Use the following command on your web browser to get a list of recordings.

http://<YOUR IP ADDRESS>:9981/api/dvr/entry/grid_upcoming

Scroll through your recordings until you find the one that matches and then look for the 32 character ‘autorec’ field.

2) Check your AutoRecs for a matching entry.

http://<YOUR IP ADDRESS>:9981/api/dvr/autorec/grid

See if you can find the same 32 character ‘uuid’ that you found previously.

This will at least show if there is an AutoRec lurking around your system somewhere and we can go from there.

Sam Malcom

DeltaMikeCharlie
My setup is running in docker, and I've restarted it a few times including when I upgraded the container somewhat recently.
I've gone to the address in your message, and none of the 3 scheduled have values present for autorec, so I've got no idea what I've done 😆

Here's one of them as an example, maybe it well help

Sam Malcom

Oh maybe I overlooked a setting that reschedules when an error is detected. I have a feeling that's what must be going on

DeltaMikeCharlie

You are recording 'Match of the day' yet the comment states 'Re-record: Auto recording: Doctor Who'.

Did you have a recording for Dr Who that was missed and rescheduled somehow?

If 'BBC1 EastHD' has reused the eventID (perfectly allowable given a suitable timespan) of a previous Dr Who episode, then it is feasible that perhaps TVH thinks that it is re-recording a missed Dr Who.

Sam Malcom

My memory is awful, so I don't know if this actually happened or not, but I suspect I created an auto recording rule for doctor who, messed it up which caused it to schedule hundreds of recordings, potentially simultaneously.

Not sure if this is a cause or a symptom, but checking just now, there were a lot of failed recordings. I think it was trying to reschedule each one, slowly chipping away at the backlog.

I've purged the failed recordings list, disabled the re-schedule on error setting and will see if that helps out