--include-threads checks for errors only after fetching threads, which is frustrating
#1,549 opened on Jun 13, 2026
Repository metrics
- Stars
- (11,684 stars)
- PR merge metrics
- (Avg merge 2d 10h) (10 merged PRs in 30d)
Description
Version
v2.47.2
Flavor
CLI (Command-Line Interface)
Platform
Windows
Export format
No response
Steps to reproduce
Export a server with --include-threads and do something that will give an error
Details
Fetching channels... Fetched 54 channel(s). Fetching threads... Fetched 334 thread(s). Attempted to export multiple channels, but the output path is neither a directory nor a template. If the provided output path is meant to be treated as a directory, make sure it ends with a slash. Provided output path: ...
It shouldn't check for errors only after fetching threads, which takes a long time. It should check for any errors before fetching anything. Currently it is frustrating having it to fetch threads and get an error, and having to fetch threads again to try to fix it.
Checklist
- I have looked through existing issues to make sure that this bug has not been reported before
- I have provided a descriptive title for this issue
- I have made sure that this bug is reproducible on the latest version of the application
- I have provided all the information needed to reproduce this bug as efficiently as possible
- I have sponsored this project
- I have not read any of the above and just checked all the boxes to submit the issue