D1 binding issue is being looked at by engineering internally, thanks for the reports.
D1 binding issue is being looked at by engineering internally, thanks for the reports.



wrangler --dev remote, or another namespace separate from your production namespace, but still deployed to cloudflares network?withSession yet, might just be coincidence, but I just deployed the worker with that change, and now the replicated D1 database is working just finewithSession()) all requests are sent to the primary explicitly. Under the hood the D1 binding has already been using the Sessions API for non replicated databases for months now, and it sends first-primary when you don't use withSession() yourself.withSession('first-unconstrained') which is working as I would expect, and not experiencing those same errorsD1_ERROR: Network connection lost. error. Sometimes after a few seconds, sometimes within a secondNetwork connection lost. are transient errors reaching the location/datacenter of your database.wrangler --dev remotewithSessionwithSession()withSession()first-primarywithSession('first-unconstrained')D1_ERROR: Network connection lost.Network connection lost.