Bulk-Verify Multiple Drives (Select + Verify + Retry)
Check 10+ drives at once for OAuth health. Select drives, bulk verify in parallel, retry failures.
What you'll learn
Enter select mode
On /drives, a toolbar appears at the top once you have 2+ connected drives. Click Select drives.
Checkboxes appear on every drive row. The button changes to show the current selection count.
Select which drives to verify
Click the checkbox on any drive you want to include. You can also use Select all personal / Select all backup buttons to pick an entire category at once.
Max 25 drives per batch — this cap exists because Google's OAuth refresh API has concurrency limits.
Run bulk verify
Click Verify N selected. Each selected drive shows a spinner while GDShine:
- Refreshes the OAuth access token
- Lists files in the drive root to prove API access
- Reports pass/fail with the exact error message on failure
Verifications run in parallel. A 25-drive check typically completes in 3-5 seconds.
Read the results
Each drive gets an inline result banner:
- Green (pass): "Connection verified — N files in root."
- Red (fail): error message + a Retry button
If the failure was a token error (invalid_grant, expired refresh token), the banner also shows a Reconnect this drive link that takes you to /connect-drive?reauth=<driveId> for an in-place token refresh.
A summary pill in the toolbar shows: ✓ 7 passed ✗ 3 failed.
Retry failures individually
Click Retry on any failed drive to re-verify just that one. This is useful after you've fixed the underlying issue (e.g., reconnected the drive, resolved a Google API hiccup).
Successful retries replace the red banner with a green one. The aggregate summary pill updates automatically.
Clear results
When you're done, click Clear results in the toolbar to remove all inline banners. Your drives are unchanged — this just tidies the UI.
Tip: run bulk verify every 1-2 weeks as a health check on your drive fleet, especially if you're running contributor-level with many drives. Expired refresh tokens silently start failing — the bulk check catches them before users notice.
You're done!
You've completed all 6 steps. Questions? Reach out to support.