#Kometa went rogue?

1 messages ยท Page 1 of 1 (latest)

astral shellBOT
#

๐Ÿ“ If you want to review this again, bsm5702:
: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> ๐Ÿ“

#

Welcome @cloud rose!

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.

astral shellBOT
#
**User Info**

Author of Linked Message: BSM
Person who Invoked the Command: BSM
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation โœ…
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - โŒ [ERROR]
Page 08: Rec 02 - โš ๏ธ [WARNING]
Page 09: Rec 03 - ๐Ÿ’ฌ CONVERT WARNING