Describe the bug
Slackdump resume runs way slower than the original archive command

Authentication type (please read)
Google

To Reproduce
I ran slackdump archive with avatars for a couple hours during the day, but then stopped it to move the database to a different internal drive on my pc because my main one was getting full. When I resumed it before going to bed I noticed it was grabbing everything a lot slower than archive was. (I also had to enable threads manually because it's enabled by default on archive but not resume?) I also stopped getting rate limited by slack. When I woke up, the archive had hardly grown in size, maybe a couple gb compared to the days' 50ish gb.

Expected behavior
Resume should have done exactly whatever archive was doing to the db

Output
Only related output is the missing slack rate limiting notifs

Desktop (please complete the following information):

• OS: Windows
• OS Version: 11
• Slackdump Version: latest (3.1.7)