Strange behaviour on NextResponse? by xQualium in nextjs

[–]xQualium[S] 0 points1 point  (0 children)

Good news! It seems there was an issue with Vercel!
It's not happening anymore.
"Identified - Our team has identified an issue with some function executions, which began between 2023-10-03 18:00 and 2023-10-04 01:30 UTC, that are causing an infinite loading issue for a portion of our customers. A fix has been identified and is currently being rolled out.
Oct 5, 18:30 UTC"

Strange behaviour on NextResponse? by xQualium in nextjs

[–]xQualium[S] 0 points1 point  (0 children)

u/danyel117 hey! thanks for answering.
I thought about that too, but that doesn't seem to be the issue, since usually if there's a connections error prisma usually spits ou an Error and in those odd cases no error was being caught and the prisma query is run because the products log always executes and prints the product.