I'm in OC so I assume the worker will be too - similar timings for deployed worker vs `wrangler dev
I'm in OC so I assume the worker will be too - similar timings for deployed worker vs
wrangler dev --remotewrangler dev --remote[WARNING] SQLite in Durable Objects is only supported in local mode., but I can probably work around that for the time being D1_ERROR: Network connection lost (even after adding retries) where every write would fail.D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be resetD1_ERROR: Network connection lost.D1_ERROR: internal error; reference = 3n7qu7dkdd0atgp7vioes6a5 589bafbd-d600-4e01-8879-7443811d45a1 if that's of any use.
wrangler pages dev may not work as expected, even when preview_database_id is set in wrangler.toml and --persist-to is used in the dev script. Runtime operations (e.g., API calls creating new data) might connect to a new, blank D1 instance instead of the schema-initialized, persisted one. This leads to "no such table" errors and data loss between development server restarts.[WARNING] SQLite in Durable Objects is only supported in local mode.D1_ERROR: Network connection lost" at D1DatabaseSessionAlwaysPrimary._sendOrThrow (cloudflare-internal:d1-api:125:19) at async D1DatabaseSessionAlwaysPrimary.batch (cloudflare-internal:d1-api:80:23) at async Object.queue (index.js:6144:5)",await env.D1.batch(
batch.map((item) => stmt.bind(...))
);D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be resetD1_ERROR: Network connection lost.D1_ERROR: internal error; reference = 3n7qu7dkdd0atgp7vioes6a5589bafbd-d600-4e01-8879-7443811d45a1wrangler pages devpreview_database_id--persist-todev