Upload Failed
Why a share upload failed and what to try next.
Use this when
You shared a recording with your team and the status badge shows Failed instead of a checkmark, or the upload progress bar stopped before reaching 100%.
Common reasons
- Lost connection mid-upload — Uploads pack and send the entire recording folder. A network drop at any point marks the upload as failed. If the app quit or crashed during an upload, the next time you open it the item is also marked failed so you can retry.
- Not signed in to a Team or Department plan — Sharing requires a Team or Department account. Free and Pro users cannot upload blobs.
- Not part of a team workspace — Your account must be associated with an org name. If sign-in completed but no org is attached, the upload will fail immediately.
- Disk or quota limit — Very large recording folders (multi-hour passes) can exceed available storage quota on your team's workspace.
- Slow connection timeout — The upload hashes the folder first, then transfers it. On a slow connection, the hash phase alone can take several minutes for large recordings.
How to check
- Hover over the Failed badge in the Shared screen. A tooltip shows the specific error message recorded at the time of failure.
- Go to Settings and confirm your account shows a Team or Department tier.
- Check that your internet connection is stable — run a speed test or load a large web page.
What to try next
- Go to Library, right-click the failed recording, and choose Share with team again. Re-sharing the same recording resets the failed state and starts the upload from scratch.
- If you are on a slow or metered connection, wait until you have a faster connection before retrying large recordings.
- Close other apps that may be using significant bandwidth during the upload.
- If the recording folder is on an external drive or SD card, make sure the drive stays connected for the full duration of the upload. Disconnecting mid-upload causes an immediate failure.
- Try sharing a shorter recording first. If that succeeds, the problem is likely a timeout on the specific large file.
If it still does not work
Contact support at support@gethumvision.com with the error text from the tooltip and the size of the recording folder. Include whether the failure happens at the hashing phase or the transfer phase.