Error: D1_ERROR: internal error; reference
Hello, been noticing these errors on and off over the past week and it causes my services to fail, even if I haven't made changes. Here's a couple of the latest ones:
"Error: D1_ERROR: internal error; reference = qmfaqrig3q4klcdqicfi02bu"
"Error: D1_ERROR: internal error; reference = uo8t49qqe0618bl2e5tl2318"
Is there anythign going on with D1 or is this related to something that I'm dong?
6 Replies
Just as info on this - my services are working now, but this was happening earlier and I've seen it sporadically over the last few days.
I was facing this error repeatedly (and randomly) - ended up changing my DB to a different location hint (eeur → enam)
and never seen this issue since
Cloudflare Docs
Data location
Learn how the location of data stored in D1 is determined, including where the leader is placed and how you optimize that location based on your needs.
Thanks. Did you have to recreate your databases to do this? Or were you able to update existing dbs with data already there?
I need to figure out something with it because it happened again today during my batch process so I have 200+ items that need to be rerun. Can’t have that everyday if at all possible
This continues to be an issue - and I see errors like this now in my services: Internal error while starting up D1 DB storage caused object to be reset. Anybody have ideas on this or what could be causing it?
I had to recreate it.
I took an export
created the new DB
uploaded everything from the export
redeployed my worker with the new DB bindings
all-in took a couple mins
Legit I was having this issue all the time and since I moved I've never seen it once
Are you also on
eeur?I don't know how to tell - I didn't add a location hint when I created the db, I did it through the dashboard. Is there a way to see what it is?
Nevermind, I didn't realize the primary region was right there on overview page. It's weird though becuse mine show up as wnam, which is probably what they should be