Your storage is full, so recordings stopped arriving
Which destination is RecordFlow archiving to? The answer, and the fix, differ.
Google Drive is full, so recordings stopped arriving
Your recordings wait safely in Zoom’s cloud — they sync automatically once there’s space, with nothing to restart.
What’s happening
Google gives every account one storage pool shared by Drive, Gmail, and Google Photos. When it’s full, Google blocks all new uploads — so recordings can’t land in your Drive. RecordFlow keeps checking and delivers everything that queued up as soon as space frees up.
The fast fix
- 1Check your storage at one.google.com/storage.
- 2Free up space: empty your Drive trash and remove large files you no longer need — or upgrade your storage with Google One.
- 3That’s it. RecordFlow notices the space and syncs the waiting recordings automatically.
Other ways to fix it
- Slim down future syncs. If you mainly need transcripts, turn on Transcript-only sync in your RecordFlow settings — it skips the large video and audio files going forward.
- Use a shared drive with room. If your organization has a shared drive with spare storage, reconnect Google Drive and pick a folder there.
- Why this hits Drive hardest. Google’s storage pool is shared across Drive, Gmail and Photos, so a full mailbox stops recordings too. The other destinations bill storage separately — switch the tabs above if you moved.
OneDrive is full, so recordings stopped arriving
Your recordings wait safely in Zoom’s cloud — they sync automatically once there’s space, with nothing to restart.
What’s happening
OneDrive storage is shared with the rest of your Microsoft account. When it’s full, Microsoft rejects new uploads — so recordings can’t land in the Apps/RecordFlow folder. RecordFlow keeps checking and delivers everything that queued up as soon as space frees up.
The fast fix
- 1Check your storage at onedrive.live.com. (On a work or school account you may be redirected through your organisation’s sign-in first.)
- 2Free up space: empty the OneDrive recycle bin and remove large files you no longer need — or add storage on your Microsoft plan.
- 3That’s it. RecordFlow notices the space and syncs the waiting recordings automatically.
Other ways to fix it
- Slim down future syncs. If you mainly need transcripts, turn on Transcript-only sync in your RecordFlow settings — it skips the large video files.
- Work account? Storage is usually set by your IT administrator, so raising the quota may be a request rather than a purchase.
- Switch destination. You can move to another destination at any time from your dashboard — see archive destinations. Recordings already archived stay where they are.
Dropbox is full, so recordings stopped arriving
Your recordings wait safely in Zoom’s cloud — they sync automatically once there’s space, with nothing to restart.
What’s happening
When your Dropbox is full, Dropbox rejects new uploads — so recordings can’t land in RecordFlow’s app folder. RecordFlow keeps checking and delivers everything that queued up as soon as space frees up.
The fast fix
- 1Check your storage at dropbox.com/account/storage.
- 2Free up space: permanently remove deleted files and delete large files you no longer need — or upgrade your Dropbox plan.
- 3That’s it. RecordFlow notices the space and syncs the waiting recordings automatically.
Other ways to fix it
- Slim down future syncs. If you mainly need transcripts, turn on Transcript-only sync in your RecordFlow settings — it skips the large video files.
- Switch destination. You can move to another destination at any time from your dashboard — see archive destinations. Recordings already archived stay where they are.
- New to Dropbox on RecordFlow? See the launch announcement for how the app folder works.
Have my YouTube uploads stopped because storage is full?
No — a YouTube channel has no storage quota to run out of, so whatever stopped your uploads, this isn’t it.
What’s happening
YouTube doesn’t bill you for space, so there is no quota to fill and no “storage full” state to get out of. Worth knowing if you connected with a Google account: your channel and your Google Drive have separate limits — a full Drive doesn’t stop YouTube uploads. Something else has stopped them.
The fast fix
- 1Start with my recordings aren’t syncing — a local (not cloud) Zoom recording is the usual cause, and it looks identical from the dashboard.
- 2Open YouTube Studio → Content and check whether the videos arrived but are still processing, or were rejected — a copyright or policy strike blocks an upload without anything appearing in RecordFlow.
- 3Check your channel’s daily upload limit. New or unverified channels are capped, and a day of back-to-back meetings can reach it; uploads resume the next day on their own.
Other ways to fix it
- YouTube only stores the video. If transcripts, chat logs or summaries are what’s missing, they were never uploaded — YouTube stores videos rather than files. Pick a file destination for those; see archive destinations.
- Switched from a file destination? Recordings archived before the switch stay where they were. Use the tabs above for the destination you were on then.
Has my S3-compatible storage bucket run out of space?
Almost certainly not — object storage has no fixed capacity to fill. Something else has stopped the writes, and it is usually billing or permissions.
What’s happening
Amazon S3, Cloudflare R2, Backblaze B2 and Wasabi all grow to fit what you put in them; there is no quota to hit, only a bill that gets larger. So “storage full” is not really a state a bucket can be in. When writes start failing, the cause is one of three things — and each looks the same from your RecordFlow dashboard.
The fast fix
- 1Check billing. A suspended account, an expired card, or a spending cap will make a provider refuse writes while leaving reads working — so the bucket looks fine when you browse it.
- 2Check the access key and bucket policy. A rotated or revoked key, or a policy that no longer allows
PutObjecton the prefix, stops writes immediately. Keys with an expiry are the common one. - 3If you self-host, check the disk. MinIO and similar endpoints do sit on real storage, and that genuinely can fill up — this is the one case where the article title is literally true.
Other ways to fix it
- Nothing is lost while it’s failing. Recordings stay in Zoom’s cloud and RecordFlow keeps retrying, so archiving resumes on its own once writes are accepted again — there is nothing to restart here.
- Costs growing faster than you expected? That is a lifecycle question rather than a fault: most providers can transition older objects to a cheaper storage class automatically. Configure that on the bucket — RecordFlow writes objects and does not manage their storage class.
- Still stuck? Send us the endpoint and bucket and the error you see in your provider’s console, and we’ll look at it with you.
Still stuck?
Contact us through our support page with what you tried and the email address on your Zoom account — we reply within one business day. Or book 15 minutes with Adam, the founder.