#Kometa Deleting and Recreating Collections
1 messages · Page 1 of 1 (latest)
Welcome @low quiver!
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.
This is an example of a collection being deleted and recreated every run ^^^
This is an example of a collection being updated only ^^^
This is an issue with some of the default collections; issue logged but no fix at present.
I don't use default collections though?
Then please provide a log file…
📝 If you want to review this again, overlord.the.ii:
: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> 📝
🚀 VERSION UPDATE AVAILABLE
Current Version: 2.2.1 (Docker: master)
Newest Version (at the time of this log): 2.2.2
Latest Kometa Versions (as of 2025-10-11 10:47:56)
Master branch: 2.2.2
Develop branch: 2.2.2
Nightly branch: 2.2.2
In the Kometa discord thread, type !update for instructions on how to update.
For more information on updating, [https://kometa.wiki/en/latest/kometa/logs/#checking-kometa-version]
2 line(s) with New Version errors. Line number(s): 11, 151033
@low quiver isn't Kometa doing literally what you tell it to? yaml delete_collections: managed: true configured: true
it's a smart collection, so it doesn't "know" how many are in the collection so the “less” doesn’t matter
I have this one too and many more that exhibit the same behavior. This is not a smart collection correct?
That delete_collections config is telling Kometa to, at the start of every run, delete all collections that were created by Kometa AND are part of the current config.
So you are asking it to delete and then recreate everything in the current config.
Ok I’ll change that and check. But I thought setting limit: 1 would mean it will delete only if less than 1 item is left in the collection?
less: 1 not limit if you're talking about the attribute under delete_collections.
Yeah that’s what I meant
Oh, and if these are smart collections they might not have a size, so that doesn't come into play.
There are a lot of twisty passages in that logic.
antwanchild used !aenh
@low quiver, 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.