you're misusing server actions, that's why

also I assume that Next/React has no way of knowing if prisma.status.whatever is stable (contrary to fetch, which it expects to be stable based on URL, params and headers, therefore it caches it) so your component that awaits getStatus() rerenders forever?

it works fine in other projects. could it be a next 14 thing?

delete the "use server" because there's no reason to go over HTTP when wanting to fetch data between a server function and a server component

prisma can't run then, might just move it to an api route

wdym prisma can't run

if i remove the 'use server' it won't fetch the data

it's still on the server even after you remove "use server"

tell that to next

that's not a next error, that's a prisma error, maybe prisma doesn't support next 14 yet

this happens in 13 as well

so prisma doesn't support RSC?

it needs 'use server' to run

hard to say, their article and demo for RSC are outdated

it works fine in several other projects. might just move it to an api layer

no "use server" here

because they aren't in a client component

i'm fetching from a client component

status is a client component? you failed to include that in the OP

there's no "use client" there

the page is, forgot to add the screenshot

i will just move it to an api route. not worth the troubles

well then I suspect the issue is that the component awaits something that doesn't look like it stabilises so it keeps rerendering forever

at least with an API route you will be aware that you need to secure it somehow

yeah. i just find it weird because i've been doing this in other projects with no issues

I'd like to point out that it's odd that your whole page is a client component

no need for it to be ssr as it's a dashboard

could go that route, though

yeah just gonna make the page ssr and wrap the interactivity in a client component

exactly