If something goes wrong
Nearly every Drive problem is one of six, and each has a one-line fix — find the message you are seeing in the left column and work across the row.
| What you see | What it means | What to do |
|---|---|---|
| "Access blocked" / "app not verified" | the client is still in Testing and the account signing in is not listed there, or the JSON belongs to a different Google account | publish the client (step 1.4) and connect again with the account whose Drive should host the files |
| Connect fails immediately | the JSON is not a Desktop app client — web clients look almost the same | create a desktop client and use its JSON |
| Token expired or revoked, typically about a week after connecting | the OAuth client is still in Testing, where Google expires refresh tokens after seven days | publish the client (step 1.4), then delete the cached token file and connect again |
| Uploads work, links don't open for Metricool | the account forbids public links | VidVertex shares each file "anyone with the link" — check the Drive account's sharing restrictions (Workspace admins can forbid them) |
| "Drive is full" / storage quota exceeded | old transfer files still sit on the Drive | clear them under Settings → Storage → Google Drive uploads, then run again |
| "No acceptable representation" from Metricool | an old error from Metricool's media endpoint | nothing but update — VidVertex has handled it since August 2026 |