Fix Mega Sync Errors — Diagnose Failed Jobs with RcloneView
Work through a failing Mega sync step by step: credentials, concurrency, logs, and a final comparison.
A Mega sync job that errors out halfway leaves you guessing: is it the login, the number of parallel transfers, or a few problem files? RcloneView puts the job settings, history, and logs in one window, so you can narrow down the cause instead of rerunning blindly.
Manage & Sync All Clouds in One Place
RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.
- One-click jobs: Copy · Sync · Compare
- Schedulers & history for reliable automation
- Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
Free core features. Plus automations available.
Start with the Remote and Credentials
Mega connects with an email and password. If jobs suddenly fail at the first step, open Remote Manager, review the Mega remote, and re-enter the credentials if the password changed. Then browse the remote in an Explorer panel: if the folder list loads, the login is fine and the problem is in the job itself.
You can also test from the built-in Terminal tab with rclone about "mymega:", which confirms the account responds before you touch any job settings.
Reduce Concurrency in the Job
Heavy parallel load is a common suspect when a backend starts erroring. Edit the job and open Step 2, Advanced Settings. Lower Number of file transfers and set Number of equality checkers to 4 or less for a slow backend. Keep Retry entire sync if fails at its default of 3 so transient failures get another chance.
Read Job History and Logs
Open Job History and look at the status, time spent, and file count of failed runs. Then check the Log tab at the bottom for the timestamped messages around the failure. To capture more detail, enable rclone Logging under Settings, set the log level to DEBUG, restart the embedded rclone, and reproduce the problem.
Preview and Verify the Fix
Run Dry Run to see what the job would copy or delete now, which is especially useful after a partial failure. Once the real job completes, use Compare between your source and Mega, filter for left-only files, and copy anything still missing.
Getting Started
- Download RcloneView from rcloneview.com.
- Re-check the Mega remote and confirm the folder list loads.
- Lower file transfers and checkers, then rerun with Dry Run first.
- Review Job History and logs, and finish with Compare.
Methodical checks turn a vague "sync failed" into a specific, fixable cause.
Related Guides:
Supported Cloud Providers
