Is it possible to create new databases dynamically yet? Or are we still stuck with being unable to o

Z

Zack•4/10/25, 8:00 PM

{"errors":[{"code":7500,"message":"internal error; reference = e_28XXLS_1d6beafaa18e4d7985c51efb410cf88e"}],"success":false,"messages":[],"result":null}

{"errors":[{"code":7500,"message":"internal error; reference = e_28XXLS_1d6beafaa18e4d7985c51efb410cf88e"}],"success":false,"messages":[],"result":null}

{"errors":[{"code":7500,"message":"internal error; reference = e_28XXLS_1d6beafaa18e4d7985c51efb410cf88e"}],"success":false,"messages":[],"result":null}

{"errors":[{"code":7500,"message":"internal error; reference = e_28XXLS_1d6beafaa18e4d7985c51efb410cf88e"}],"success":false,"messages":[],"result":null}

P

Paul Shriner - Titleless•4/10/25, 8:05 PM

Hoping it is just a restart issue.

T

Tim•4/10/25, 8:07 PM

I'm also having issues with D1.

Dashboard

When trying to load my list of databases, the

GET https://dash.cloudflare.com/api/v4/accounts/X/d1/database?page=1&per_page=25

GET https://dash.cloudflare.com/api/v4/accounts/X/d1/database?page=1&per_page=25

GET https://dash.cloudflare.com/api/v4/accounts/X/d1/database?page=1&per_page=25

GET https://dash.cloudflare.com/api/v4/accounts/X/d1/database?page=1&per_page=25 returns a 500 like,

{
    "errors": [
        {
            "code": 7500,
            "message": "internal error; reference = e_28XXLS_d2cd6b5618884603b87fab149025c82e"
        }
    ],
    "success": false,
    "messages": [],
    "result": null
}

{
    "errors": [
        {
            "code": 7500,
            "message": "internal error; reference = e_28XXLS_d2cd6b5618884603b87fab149025c82e"
        }
    ],
    "success": false,
    "messages": [],
    "result": null
}

{
    "errors": [
        {
            "code": 7500,
            "message": "internal error; reference = e_28XXLS_d2cd6b5618884603b87fab149025c82e"
        }
    ],
    "success": false,
    "messages": [],
    "result": null
}

{
    "errors": [
        {
            "code": 7500,
            "message": "internal error; reference = e_28XXLS_d2cd6b5618884603b87fab149025c82e"
        }
    ],
    "success": false,
    "messages": [],
    "result": null
}

---

Deployment

My deployment of a "Page w/ Worker", which has a D1 binding is failing with the following,

Error: Failed to publish your Function. Got error: binding DB of type d1 failed to generate. Please try again later or contact support.

Error: Failed to publish your Function. Got error: binding DB of type d1 failed to generate. Please try again later or contact support.

Error: Failed to publish your Function. Got error: binding DB of type d1 failed to generate. Please try again later or contact support.

Error: Failed to publish your Function. Got error: binding DB of type d1 failed to generate. Please try again later or contact support.

N

nejc•4/10/25, 8:09 PM

Same problem here

N

nejc•4/10/25, 8:09 PM

{"errors":[{"code":7500,"message":"internal error; reference = e_28XXLS_75dd26695d58424fb92679a4a8ca2038"}],"success":false,"messages":[],"result":null}

N

nejc•4/10/25, 8:09 PM

I am getting this on all databases that I tried (and we have thousends of them)

I

Isaac McFadyen•4/10/25, 8:11 PM

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

P

Paul Shriner - Titleless•4/10/25, 8:12 PM

AND WERE BACK

MMissS Is it possible to create new databases dynamically yet? Or are we still stuck wi...

A

ajgeiss0702•4/10/25, 8:15 PM

dynamic bindings are not released yet. Until they are, Durable Object's SQL storage is something you could look into, since you can create an unlimited number of objects, and each has seperate storage.
Note: https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/#sql-in-durable-objects-vs-d1

Aajgeiss0702 this chart on the blog post gives me the impression that read replicas will pret...

L

lambrospetrou•4/10/25, 8:21 PM

Unless there is an incident the normal replication lag is a round trip from the primary to the replicas, yes.

Llambrospetrou Unless there is an incident the normal replication lag is a round trip from the ...

A

ajgeiss0702•4/10/25, 8:21 PM

cool, thank you

S

Samantas5855•4/10/25, 8:22 PM

Ive been facing issues, not all my api pushes make it to the database

S

Samantas5855•4/10/25, 8:22 PM

I assume Im not the only one

Z

Zack•4/10/25, 8:23 PM

IIsaac McFadyen D1 binding issue is being looked at by engineering internally, thanks for the re...

A

ajgeiss0702•4/10/25, 8:24 PM

Z

Zack•4/10/25, 8:24 PM

Getting this on just the replicated database that I am testing in dev, not even switched to the session syntax yet

I

Isaac McFadyen•4/10/25, 8:24 PM

See my message above (if Discord is working enough for it to come in, haha - they're also having an incident)

Z

Zack•4/10/25, 8:25 PM

Apologies, I thought that was with reference to people having trouble spawning workers with D1 bindings, missed the other messages with similar errors

ZZack Apologies, I thought that was with reference to people having trouble spawning w...

I

Isaac McFadyen•4/10/25, 8:26 PM

No worries - yeah I don't know specifics of what would be affected, just that some internal API is having issues, R2+D1 are affected, and that engineering is engaged internally

Z

Zack•4/10/25, 8:26 PM

Fair enough, my main addition then is that this isn't affecting our production databases, just this one with replication enabled. Unsure if that's relevant or just coincidence

N

Nikolas•4/10/25, 8:27 PM

The problem we currently face is, when the d1 write succeeds and doesn't throw "internal error", it doesn't write all the columns, only the first ones. We do a big insert query through the API. I assume there is a grater issue with d1 right now?

NNikolas The problem we currently face is, when the d1 write succeeds and doesn't throw "...

I

Isaac McFadyen•4/10/25, 8:28 PM

There is but I'm not sure if that would be a result of the issues or not, sorry.

IIsaac McFadyen D1 binding issue is being looked at by engineering internally, thanks for the re...

D

datacenterdude•4/10/25, 8:45 PM

Appears to be back online! Appreciate the quick response to the team!

I

Isaac McFadyen•4/10/25, 8:45 PM

Yup, issues should be resolved! Thanks again for reporting

IIsaac McFadyen Yup, issues should be resolved! Thanks again for reporting 😄

Z

Zack•4/10/25, 8:55 PM

Still seeing issues, though different

Z

Zack•4/10/25, 8:57 PM

Correction, still seeing the same errors from before:

ZZack Still seeing issues, though different

C

Chaika•4/10/25, 9:30 PM

how frequent?

CChaika how frequent?

Z

Zack•4/10/25, 9:32 PM

Every request when I was testing

C

Chaika•4/10/25, 9:33 PM

do you have replication enabled on the db? I see some on my replicated db, but none w/o

Z

Zack•4/10/25, 9:33 PM

I can test again shortly

CChaika do you have replication enabled on the db? I see some on my replicated db, but n...

Z

Zack•4/10/25, 9:33 PM

Yes, replicated, non replicated databases are totally error free

Z

Zack•4/10/25, 9:33 PM

FWIW this isn't a big issue for me, but if it's more widespread I am happy to help with providing errors and retesting

Z

Zack•4/10/25, 9:33 PM

I am just testing the replicated d1 in dev right now but it just won't work for any requests

S

Samantas5855•4/10/25, 9:54 PM

apparently my issues seem to be due to caching in pages functions

ZZack I am just testing the replicated d1 in dev right now but it just won't work for ...

M

Milan•4/10/25, 10:36 PM

Dumb question but wdym "in dev"?

MMilan Dumb question but wdym "in dev"?

Z

Zack•4/10/25, 10:37 PM

As in, our dev environment

Z

Zack•4/10/25, 10:37 PM

I've not pushed using replication into our production environment yet, so it's not a big issue for me

Z

Zack•4/10/25, 10:37 PM

I am still experiencing the problems though

M

Milan•4/10/25, 10:37 PM

Like, running

wrangler --dev remote

wrangler --dev remote

wrangler --dev remote

wrangler --dev remote, or another namespace separate from your production namespace, but still deployed to cloudflares network?

Z

Zack•4/10/25, 10:38 PM

All deployed to cloudflare, we deploy via terraform

Z

Zack•4/10/25, 10:38 PM

Seperate database to production

Z

Zack•4/10/25, 10:38 PM

It's "production" as far as you guys know

M

Milan•4/10/25, 10:41 PM

Thanks for clarifying!

MMilan Thanks for clarifying!

Z

Zack•4/10/25, 10:46 PM

Some more info, I disable read replication on the database, redeployed the worker, everything worked fine. Enabled replication again, redeployed the worker, constant errors again

Z

Zack•4/10/25, 10:46 PM

D1 ID: c60521e7-59bd-4186-81e7-9a676edf9b75
Incase you wanted to look into it. If you need the worker ID, just lmk what specifically you need

Aajgeiss0702 db id is `221100ba-5ab9-4cda-8cfa-69c17ea546ab` if it helps (account id is `f55b...

A

ajgeiss0702•4/10/25, 10:59 PM

i am also getting the issue occassionally

MMilan Thanks for clarifying!

Z

Zack•4/10/25, 11:04 PM

Sorry to reply one more time, but I just wanted to say that I hadn't moved to use

withSession

withSession

withSession

withSession yet, might just be coincidence, but I just deployed the worker with that change, and now the replicated D1 database is working just fine

ZZack Sorry to reply one more time, but I just wanted to say that I hadn't moved to us...

M

Milan•4/10/25, 11:22 PM

I'm not familiar enough with D1's API to know whether this would cause problems or not, but can get back to you tomorrow

Z

Zack•4/10/25, 11:23 PM

My understanding is that without using the session API it will only ever route to the primary instance of D1

Z

Zack•4/10/25, 11:23 PM

But it shouldn't just fall over and constantly fail

Is it possible to create new databases dynamically yet? Or are we still stuck with being unable to o

Similar Threads

Similar Threads

Similar Threads