#Trakt Errors- How can I resolve them?

1 messages · Page 1 of 1 (latest)

quartz bladeBOT
#

Welcome @vital coral!

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.

#

📝 If you want to review this again, traderr.2287:
: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> 📝

quartz bladeBOT
#

Below is my config file portion of Trakt. I used the Wiki Generator to create this but sill got the erors in the log. Not sure how to filx these
########## GENERATED BY TRAKTAUTH ##########
trakt:
client_id: (redacted by Luma)
client_secret: (redacted by Luma)
authorization:
access_token: (redacted by Luma)
token_type: Bearer
expires_in: 604799
refresh_token: (redacted by Luma)
scope: public
created_at: 1769643307

############################################

rain trail
#

There are no trakt errors in that log.

[INFO]     | Connecting to Trakt...
[WARNING]  | Config Warning: trakt sub-attribute pin not found using None as default
           | trakt sub-attribute pin added to config
[WARNING]  | Config Warning: trakt sub-attribute force_refresh not found using None as default
           | trakt sub-attribute force_refresh added to config
[INFO]     | Trakt Connection Successful

There are two warnings saying that a couple Trakt settings that you don't need are not present and are being defaulted and added to the config, but no errors.

#

The log actually contains no errors of any kind.

vital coral
#

Ok - Great, I will go ahead and remove them. Thank you!

rain trail
#

remove what?

#

If you remove those two settings the same thing will happen the next run

#

Don't "fix" non-errors

#

You don't need them because your trakt connection is working fine, but Kometa tries to read them, sees that they are missing and fills them in with the default values. Let it do that.

vital coral
#

Ok, I was thinking that I should remove the force_refresh and PIN Sub attribute but if they're not actually errors and just warnings I understand the logic.

rain trail
#

They don't say ERROR; they say WARNING. They aren't ERRORs

vital coral
#

Ok- Got it, thank you again.