Troubleshoot Transfer Manager
Invalid API Key
Almost always the wrong region, not a bad key. RTM's platform selection must match the account the key came from. A valid US key fails against the EU platform with this exact error.
Check the region against the table in setup. If it's right, check whether the key expired, API keys carry expiration dates, visible in Preferences > API. Add a new key and re-enter it.
Full steps: Resolving "Invalid API Key" error.
Path or file name too long
Windows enforces a 260-character limit on full paths. Job output nested a few levels deep, downloaded into an already-deep local folder, exceeds it easily.
Fix by choosing a shorter destination, C:\r\ rather than a path under Documents and a project tree. See RTM download fails: path or file name too long.
Rescale caps name plus path at 200 bytes when files are stored. That's a different limit with a different failure mode: see upload files.
SSL or certificate errors
Your network is intercepting TLS, or a firewall is blocking one of the object-storage endpoints RTM needs. See the network access list, then Troubleshooting SSL certificate errors.
A task was canceled
Usually a dropped connection or a timeout mid-transfer. RTM resumes, so retry first. If it recurs, Troubleshooting "a task was canceled".
The deployment identity does not match the subscription
A configuration mismatch between the installed client and your account. See RTM error: deployment identity does not match the subscription.
Transfers blocked entirely
Not an RTM problem. You may have hit an enforced transfer limit. Check current usage before debugging the client.
Collecting logs for support
Before opening a case, grab the logs: How to access and save RTM logs.
Related
- Transfer Manager overview — setup and network requirements
- Download with RTM
- Limits and policies