Unknown Error: 'data' in creating playlist

[spare trench]

Hello everyone,
I have a problem with playlists. When I launch them, I get an imdb_list error, even though I haven't left this field in any of my files. I've made sure that it points to trakt links, but I don't understand why it can't take them into account. Attached is the log file for the command and my playlist.yml configuration files.
Can u help me?

[ebon shoal]

Welcome @spare trench!

It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

You can press the "Close Post" button above or type /close at any time to close this post.

[full mulch]

Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯_(ツ)_/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Kometa

[spare trench]

here is my meta.log:

[ebon shoal]

📝 If you want to review this again, darklag:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

[glossy badger]

This was caused by a change on the IMDB side and is fixed in Kometa nightly.

The playlists have IMDB lists as their sources.

[spare trench]

so how i can upgrade to nighlty?

[glossy badger]

!branch

[full mulch]

If you are looking for guidance on how to switch branches of Kometa, please type one of the following commands

!branchgit if you are running Kometa locally (i.e. you cloned the repository using Git)

!branchdocker if you are running Kometa within docker

!branchunraid if you are running docker on Unraid

Moving between branches using Docker

NOTE: This is addressing changing from, for instance, latest to nightly.

replace IMAGE_NAME with kometa, imagemaid, or overlay-reset; whichever image you want to switch branches on.

replace BRANCH_NAME with latest, develop, or nightly; whichever you want to switch to.

The command to update/download the docker image is:

docker pull kometateam/IMAGE_NAME:BRANCH_NAME

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.], setting the image as kometateam/IMAGE_NAME:BRANCH_NAME

Thanks for using Kometa

[spare trench]

thanks i test that!

[full mulch]

chazlarson used !aenh

@spare trench, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.