Describe the bug
slackdump resume -threads doesn't fetch new threads on old messages that previously had no threads.
To Reproduce
- In Slack, write a message in
- Create a new archive: `slackdump archive -o test_archive
- In Slack, start a new thread on the message from step 1
- Run
slackdump resume -threads test_archive
- View the archive
Expected behavior
The thread from step 2 should appear in the test archive.
Output
The thread won't be there. (Threads on new top-level messages will be there, and so will updates on threads that already existed in the archive.)
Desktop (please complete the following information):
- OS: Ubuntu
- OS Version: 25.04
- Slackdump Version: 3.1.10
Additional context
As described in #550 , resume -threads already has to request updates on every existing thread in the DB. Fixing this might make that even slower!
Would it be possible to allow specifying a timeframe (e.g. "30 days before the end_time of the previous run") where resume -threads does thread-checking only for messages/replies in the archive that are within that timeframe? (Let me know if this should be a separate feature request.)
Describe the bug
slackdump resume -threadsdoesn't fetch new threads on old messages that previously had no threads.To Reproduce
slackdump resume -threads test_archiveExpected behavior
The thread from step 2 should appear in the test archive.
Output
The thread won't be there. (Threads on new top-level messages will be there, and so will updates on threads that already existed in the archive.)
Desktop (please complete the following information):
Additional context
As described in #550 ,
resume -threadsalready has to request updates on every existing thread in the DB. Fixing this might make that even slower!Would it be possible to allow specifying a timeframe (e.g. "30 days before the end_time of the previous run") where
resume -threadsdoes thread-checking only for messages/replies in the archive that are within that timeframe? (Let me know if this should be a separate feature request.)