Internal error occurred - Contact support

Hi We are getting the following error from time to time since yday. It gets resolved by it self when manually retrying the build:
22:34:13.230 Cloning repository...
22:34:14.381 From https://github.com/***/***
22:34:14.382 * branch 5401d3b1cf667acbb480a9f36502b2d27e0bf2a9 -> FETCH_HEAD
22:34:14.382
22:34:14.482 HEAD is now at 5401d3b Add blur handler to date input
22:34:14.483
22:34:14.595
22:34:14.631 Success: Finished cloning repository files
22:37:38.882 Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
22:34:13.230 Cloning repository...
22:34:14.381 From https://github.com/***/***
22:34:14.382 * branch 5401d3b1cf667acbb480a9f36502b2d27e0bf2a9 -> FETCH_HEAD
22:34:14.382
22:34:14.482 HEAD is now at 5401d3b Add blur handler to date input
22:34:14.483
22:34:14.595
22:34:14.631 Success: Finished cloning repository files
22:37:38.882 Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
Attached you'll see two examples. This behavior started just yesterday when we updated our SvelteKit app to 2.0 along with the CloudFlare adapter. We are using version 2 of the build system. And we are using node 20.10.0. The IDs of failed deployments so far are: - 9b677520-a3d2-44f4-aa5e-fcc3340c254b -> fixed automagically here: 449a1e7c-bc6f-4f05-8bdf-161fdf883329 - 276247a1-4ad2-4e3e-94eb-a1218b3bd6d3 -> fixed automagically here: 90442989-4266-4416-95e1-62c7336953aa - 16627ba0-095f-4e24-8eaf-dcfb16aab99a -> fixed automagically here: 21f3ed7f-b5a4-43b1-9bd9-34fbb19207a3 Any idea of what we could try?
No description
No description
2 Replies
Erisa
Erisa5mo ago
@feva these indeed seem to be caused by an internal error on our side, we're having a look to see if it's something we can fix. I don't think it's related to your project but will let you know if it turns out that way
feva
feva5mo ago
@Erisa | Support Engineer thank you very much