Allow Threads to be Programmatically Made "Inactive" #6703
Replies: 4 comments
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
This would be very helpful. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions