@awb This was due to an incompatibility between the format of certain responses returned by the API and how the SDK was parsing them. The team updated the server to return responses that the SDK would parse successfully. There may be other cases of this though, so if you're seeing this currently, please share several (5-10) sample 'X-Dropbox-Request-Id' response header values for these failures, along with the corresponding timestamps and timezones for each so we can check on them. Thanks in advance!
@Greg-DB thanks for the quick response. We ran this again and did not encounter the error. Not sure if anything changed on the Dropbox side. If we encounter this again, I'll send through the requests ids.
Thanks