Allow Threads to be Programmatically Made "Inactive"

[thomasloupe]

Context: A bot that migrates chat history from another chat service that supports threaded discussions, to a Discord guild.

Problem:
Discord allows 1000 active threads guild-wide, but there is no way to programatically mark a thread as "inactive". This breaks chat migration bots completely as they are able to hit the limit before the lowest archive setting (1 day). Additionally, manually marking a thread programmatically as "archived" still counts toward the active thread limit. The only workaround is to set the default thread archive to 1 day, migrate a single channel a day and wait for threads to become inactive naturally before importing another channel that would otherwise might/might not surpass the thread limit depending on active thread count. This workaround clearly does not account for channels that have 1000 active threads themselves, which would still return a max threads reached error.

Proposed solution(s):
Either allow threads marked programmatically as "archived" as "inactive" as well.

or

Define an "active" property boolean value specifically made for this functionality alongside the existing archive functionality. This allows developers to programmatically mark a thread as "inactive", which automatically marks the thread as "archived" as well, but with added benefit that threads can also be marked as "active + archived" or "active + unarchived".

In the provided context, it's important to maintain consistency in the chat history formats as users expect.

[iainhallam]

This is potentially stopping me migrating a long chat history at the moment; please allow a way for a bot to reduce the active thread count where needed.

[erkinalp]

Define an "active" property boolean value specifically made for this functionality alongside the existing archive functionality. This allows developers to programmatically mark a thread as "inactive", which automatically marks the thread as "archived" as well, but with added benefit that threads can also be marked as "active + archived" or "active + unarchived".

active could be defined as archived NOR locked

[astrodad]

This would be very helpful.

[sc0ttkclark]

I would really enjoy having the ability because I'm trying to import a server with hundreds of thousands of messages and soooo many threads because we used them extensively.

[ManHatos]

It doesn't matter how the thread was made archived, they are all treated the same :)

From https://discord.com/channels/613425648685547541/1130595287078015027/1261479894135738471

[thomasloupe]

Thanks for the reply!
I've responded there in the Discord thread on that subject. I think many people, including myself, are quite confused then on what keeps a thread "active".

We're all open to understanding and learning if we're incorrect on how to achieve closing threads and keeping them viewable while not counting toward the limit.

[sc0ttkclark]

Which discord is that? The link is being weird on the mobile Discord app itself

[thomasloupe]

The Official Discord Developers discord. :)

[ManHatos]

We're all open to understanding and learning if we're incorrect on how to achieve closing threads and keeping them viewable while not counting toward the limit.

According to the staff, setting archived: true on threads should in fact not count towards the limit, if you experience otherwise it is probably better to open a bug report.