Docs

Troubleshooting a Failed Transfer

Transfers occasionally fail — a source going offline, a provider rate limit, an expired token. Here's how to diagnose and fix it.

The short version

  • Failed jobs never consume quota, so retrying costs you nothing
  • Most failures are retryable directly from your feed, no need to start over
  • An expired connection token shows a clear reconnect prompt, not a silent failure

In practice

  1. Open your feed and find the failed job — the reason is shown next to it.
  2. If it's a connection issue, reconnect the provider from Connections.
  3. Retry the job directly from the feed.

FAQ

Why did my transfer fail partway through?

Most commonly: an expired provider connection token, a source that became unavailable mid-transfer, or a provider-side rate limit. The feed shows the specific reason.

Do I lose anything that already transferred before the failure?

No — a partial transfer isn't counted, and retrying starts the job fresh rather than leaving a corrupted partial file.

All docsFrequently asked questions