Network Errors

A network error is an upload request that failed on the way: a timeout, a dropped connection, a proxy or Cloudflare error, or a busy server answering 503, 429 or 508. It is about the connection, not the file.

What Flying Pigs does

Flying Pigs sends every failed request again, automatically. The files in it still land. The run carries on while the retries happen.

• A request that gets no answer in 180 seconds is treated as failed and sent again.
• If the server refuses a request as too large, the next ones go out smaller.
• With Pro's turbo boost, a server that answers 503, 429 or 508 drops the run to two lanes, so it stops pushing a host that is already struggling.
• If your WordPress login expires during a run, the run pauses. Log in again in another tab, then press Resume.

The run stops only when requests keep failing for the whole Upload timeout in the Advanced panel, 370 seconds by default, without a single successful upload. The summary card is then titled Upload Network Error.

Where to see them

Once a request fails, a Network errors button appears beside the run buttons. It shows failed requests over all requests in this run, for example 3 / 412, and starts again at zero on each run. Click it for each error with its time and reason. The summary card also says how many network errors were recovered by retry.

If they keep happening

• A few recovered errors in a big run are normal, especially over Wi-Fi, a VPN or Cloudflare.
• If the host keeps answering 503, 429 or 508, it is throttling you. Lower Batch size limit, set a Server IO limit or Files per second, or turn on Pause uploads in the Advanced panel. In Pro, leave Upload lanes on Auto.
• A security plugin with rate limiting, such as Wordfence, can block a burst of batch requests. Raise its limits for logged-in users.
• If a run stops with Upload Network Error, check your connection and that the site loads, then start the run again. Files that already landed stay in the library.