Troubleshooting & messages · Background service, pauses and self-healing

Why does Services say transfers are queued but not starting?

Short answer: Queued transfers wait for what they depend on — a signed-in account, internet, or the drive. Open Data Transfers to see each job's reason and resume or retry it.

Transfers wait in the queue when something they depend on isn't ready — commonly a cloud account that needs signing in again, no internet connection, or the external drive being unplugged.

Open Data Transfers to see each job's state. A failed job shows its reason; a paused one has a resume option. If an account needs signing in again, reconnect it in Remotes & Accounts.

See Data Transfers.

Last reviewed

Also available as Markdown and JSON.