Troubleshooting
wrangler dev and wrangler tail are both available to help you debug your Durable Objects.
The wrangler dev command opens a tunnel from your local development environment to Cloudflare’s global network, letting you test your Durable Objects code in the Workers environment as you write it.
wrangler tail displays a live feed of console and exception logs for each request served by your Worker code, including both normal Worker requests and Durable Object requests. After running npx wrangler deploy, you can use wrangler tail in the root directory of your Worker project and visit your Worker URL to see console and error logs in your terminal.
In your wrangler.toml file, make sure the dir and main entries point to the correct file containing your Worker code, and that the file extension is .mjs instead of .js if using ES modules syntax.
When deleting a migration using npx wrangler deploy --delete-class <ClassName>, you may encounter this error: "Cannot apply --delete-class migration to class <ClassName> without also removing the binding that references it". You should remove the corresponding binding under [durable_objects] in wrangler.toml before attempting to apply --delete-class again.
A single instance of a Durable Object cannot do more work than is possible on a single thread. These errors mean the Durable Object has too much work to keep up with incoming requests:
Error: Durable Object is overloaded. Too many requests queued.The total count of queued requests is too high.Error: Durable Object is overloaded. Too much data queued.The total size of data in queued requests is too high.Error: Durable Object is overloaded. Requests queued for too long.The oldest request has been in the queue too long.Error: Durable Object is overloaded. Too many requests for the same object within a 10 second window.The number of requests for a Durable Object is too high within a short span of time (10 seconds). This error indicates a more extreme level of overload.
To solve this error, you can either do less work per request, or send fewer requests. For example, you can split the requests among more instances of the Durable Object.
These errors and others that are due to overload will have an .overloaded property set on their exceptions, which can be used to avoid retrying overloaded operations.
There is a limit on how quickly you can create new Durable Objects or lookup different existing Durable Objects. Those lookups are usually cached, meaning attempts for the same set of recently accessed Durable Objects should be successful, so catching this error and retrying after a short wait is safe. If possible, also consider spreading those lookups across multiple requests.
Reset in error messages refers to in-memory state. Any durable state that has already been successfully persisted via state.storage is not affected.
Refer to Global Uniqueness.
To prevent indefinite blocking, there is a limit on how much time storage operations can take. In Durable Objects containing a sufficiently large number of key-value pairs, deleteAll() may hit that time limit and fail. When this happens, note that each deleteAll() call does make progress and that it is safe to retry until it succeeds. Otherwise contact Cloudflare support.
Besides the suggested approach of backing off, also consider changing your code to use state.storage.get(keys Array<string>) rather than multiple individual state.storage.get(key) calls where possible.