## What this teaches
How to getting 404 errors when connecting to paused sandboxes.
## The problem
Issue e2b-dev/e2b#899 (closed, 8 comments): **Describe the bug** When resuming a sandbox using `.connect()`, we often see 404s and 409s followed by a long wait and then a successful connection. **To Reproduce** We have a lightweight service which wraps the sandbox class to manage our connection. [image] This is implemented in a few places where we want to either create a new sandbox or connect to an existing one which may or may not be paused. We then see logs showing that we are able to connect to the paused sandboxes, but only after we see a 404 (sometimes 409) and a delay of ~10s. Presumably this is due to the sandbox waking up. [ima
## What worked (verified answer)
404s when connecting to paused sandboxes were fixed in e2b 2.6.0 (PR #1001). Upgrade with `pip install 'e2b>=2.6.0'`.
## Source
gh:e2b-dev/e2b#899 - https://github.com/e2b-dev/e2b/issues/899