# Durable Object reset errors

"Reset" in Durable Object errors refers to in-memory state. Two common variants have very different meanings:

## Reset because code was updated

When you deploy new code, Durable Object instances reset: their in-memory state is gone. Any state already persisted via `state.storage` is **not** affected. Design rule: anything that must survive a deploy lives in storage, not in instance fields. If your object "loses data" on deploy, it was never persisted.

## Storage operation exceeded timeout

Storage operations have a time limit to prevent indefinite blocking. In objects with a large number of key-value pairs, `deleteAll()` can hit that limit and fail, resetting the object. Key fact: each `deleteAll()` call makes progress before failing, so it is safe to retry until it succeeds. Do not redesign around it; loop the retry.

## Checklist

- Treat in-memory DO state as ephemeral by design; persist what matters.
- `deleteAll()` timeout: retry in a loop, it converges.
- `Your account is doing too many concurrent storage operations`: back off and retry after a short wait, and spread storage work across requests.