Read Timeout

TL;DR

The SDK added 'Connection reset by peer' to the retried exceptions in version 3.6.2, and planned 'Read timed out' for a following release. Fix: upgrade box-python-sdk to 3.6.2 or later so transient connection drops are retried automatically instead of killing your script.

Steps

1. Read timeouts (and 'Connection reset by peer') in long-running box-python-sdk scripts were not retried by default. The SDK added 'Connection reset by peer' to the retried exceptions in version 3.6.2, and planned 'Read timed out' for a following release. Fix: upgrade box-python-sdk to 3.6.2 or later so transient connection drops are retried automatically instead of killing your script.

When to use

You are seeing this: Reported in Box: Read Timeout. Use this skill when you run into "Read Timeout".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 3.6.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:box/box-python-sdk#789 (https://github.com/box/box-python-sdk/issues/789), the reporter ran into this: Reported in Box: Read Timeout. The verified resolution: Read timeouts (and 'Connection reset by peer') in long-running box-python-sdk scripts were not retried by default. The SDK added 'Connection reset by peer' to the retried exceptions in version 3.6.2, and planned 'Read timed out' for a following release. Fix: upgrade box-python-sdk to 3.6.2 or later so transient connection drops are retried automatically instead of killing your script.