I noticed the other day that recording schedule for my favorite baseball team stopped recording in mid June. I attempted to delete the schedule and recreate it in case something weird happened in the team metadata. When I try to recreate it, an error is displayed in the schedule dialog, and the exact same two SQL errors that have been shown in all of the other threads are shown in the logs as the error is displayed in the dialog.
Jul 14, 2025 14:33:54.464 [140419978967864] ERROR - [Req#2549d7] SQLITE3:0x80000001, 1, no such column: media_items.begins_at in "select metadata_items.id from metadata_items left join metadata_items as parents on parents.id=metadata_items.parent_id left join metadata_items as grandparents on grandparents.id=parents.parent_id where (metadata_items.id in (select taggings.metadata_item_id from taggings join tags on tags.id=taggings.tag_id where tags.id=1029) and metadata_items.metadata_type=4) order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc"
Jul 14, 2025 14:33:54.464 [140419978967864] ERROR - Got exception from request handler: sqlite3_statement_backend::prepare: no such column: media_items.begins_at for SQL: select metadata_items.id from metadata_items left join metadata_items as parents on parents.id=metadata_items.parent_id left join metadata_items as grandparents on grandparents.id=parents.parent_id where (metadata_items.id in (select taggings.metadata_item_id from taggings join tags on tags.id=taggings.tag_id where tags.id=1029) and metadata_items.metadata_type=4) order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc
Given that the SQL error is the same as displayed earlier in the thread and the issues are all related to Live TV/DVR, it seems like the underlying issue is the same. If Plex needs yet another thread to diagnose this, I can start one, but it seems like there are enough of them already.
Can you please download your PMS logs and share them with me? As I mentioned above, the next Beta release will have the fix for the Browse page not loading. When it’s available could you try it out against your issue?
The update to v1.42.0.9975 seems to have fixed the problem that I reported when I started the original thread. Searching on the EPG also seems to work, which was another problem noted in other threads. I tested it on an old MacMini. I’m waiting until I see more reports before I install it on my regular MacMini.
I just messed with this a bit more on my main Plex NAS - 1.41.9.9961 Synology 7.2.2.
I can schedule recordings for individual Detroit Tigers baseball games without error. I can schedule the “All MLB Baseball Events” option without error. Things error out when I try to create a schedule for “All Detroit Tigers Events”. This also leaves behind non-functional recording schedules which I cannot delete, pictured below.
Is the Airings option set to “New Airings Only” or “New and Repeat Airings”? You will need to cancel the existing recording scheduled and create a new one in order to change this setting.
Selecting any of those recordings should open a prompt to allow for editing the recording, including cancelation of the recording.
All were set to record new episodes only. Attempts to remove the “All Detroit Tigers Events” schedules result in an on-screen error in the UI and the two database errors in the logs that have been previously pasted into the thread.
Jul 22, 2025 16:10:05.048 [140123604110136] ERROR - [Req#703077] SQLITE3:0x208, 1, no such column: media_items.begins_at in "select metadata_items.id from metadata_items left join metadata_items as parents on parents.id=metadata_items.parent_id left join metadata_items as grandparents on grandparents.id=parents.parent_id where (metadata_items.id in (select taggings.metadata_item_id from taggings join tags on tags.id=taggings.tag_id where tags.id=1034) and metadata_items.metadata_type=4) order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc"
Jul 22, 2025 16:10:05.048 [140123604110136] ERROR - Got exception from request handler: sqlite3_statement_backend::prepare: no such column: media_items.begins_at for SQL: select metadata_items.id from metadata_items left join metadata_items as parents on parents.id=metadata_items.parent_id left join metadata_items as grandparents on grandparents.id=parents.parent_id where (metadata_items.id in (select taggings.metadata_item_id from taggings join tags on tags.id=taggings.tag_id where tags.id=1034) and metadata_items.metadata_type=4) order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc
What version of PMS are you using currently? The current beta has a fix for a Live TV issue that looks similar to the log entries you shared.
If possible could you give the Beta a spin to see if this resolves the error message.
In my experience some “airings” need to have the “New and Repeat Airings” set in order to pick up future airings. I’ll ask around about this, because these should be considered New Airings.
I’m not really willing to be a beta software guinea pig for products that I pay for, so I trust that you’ll be able to replicate the issue in the secret underground Plex laboratory bunker using the data provided. If you need more information, I’m happy to send more logs.
If the issue is fixed in that beta, I’ll discover that when it goes into a stable/production state and I’ll report back.
I can confirm I’m affected by this as well. Just Mets games. Looks specific to “all xxx airings” option compared to single recording. When recreating the schedule, it errors out, but the schedule gets created. When deleting it, I get an error, but it deletes. Missed three days of recordings, and doesn’t see any new ones going forward. Running 1.41.9.9961 on Syno 6.2.
@dgarra Also, you and @d0ct0rvenkman could either/both of you provide the entire zip of your PMS logs? I cannot easily reproduce here.
In regards to the above quote, the need to use “New and Repeat Airings” for some items is due to a lack of metadata which causes the issue where truly New airings are not correctly identified as such, resulting in the missed recording.
@dgarra Would you be able/willing to install the latest Beta? Another path forward might be to simply uninstall your PMS and reinstall the same version. It appears like a DB migration task may not have ran during one of your upgrades to 1.41.9. Another path would be to use Chuck’s DB Repair tool to attempt to repair the DB.
If none of these are something that you’d want to do, could you please download your DB and share it with me? This way I can work with an affected DB, as I cannot reproduce with a fresh install or downgrading back to 1.41.9. It’d probably be best to share via DM. @d0ct0rvenkman too.
Since I installed the current beta ( 1.42.0.9975) I have not had any problems scheduling recordings. Although they don’t involve sports events, I have several scheduled programs and they have all been recorded successfully.
I installed the beta and recreated the schedule. It does acknowledge future events, and doesn’t error out, so that’s encouraging. Gametime today is 9:30PM ET, I’ll see if it records.
I’ve also noted the same behavior on a rarely-used Plex instance I have at my family’s vacation place. I’m far less risk-averse with that machine, so I can potentially experiment a bit more.
@Atomatth - you mention that there are DB migrations that may have not been run on the 1.41.9 instances… are those something you can share to see if a 1.41.9 version can be fixed by making sure those DB migrations have been applied?
Also, you and 
