turn out nextjs is just caching first request and not sending new one

the new cache system is frustating

can i disable it on my api routes?

i tried to do fetch no store in the frontend but that didn't fix it

Honestly I don't know too

Thank you that's half the answer

The answer was that

first add

export const dynamic = 'force-dynamic'

then the response had to be dynamic because my response was

{Success: true}

so i had to put something changing so it ended up doing

{Success: `true ${Math.random()}`

not the best approach but worked

Checkout :
https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#revalidate:~:text=to%20false.-,revalidate,-Set%20the%20default

and https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#revalidating-data:~:text=Data%20Cache.-,Revalidating%20Data,-Revalidation%20is%20the

so, it worked, can you mark this post as solved?

how can i do that?

Select the message that helped you solve this, apps -> mark as solution

^

Can you please explain you solution a bit more like, where did you do
{Success: `true ${Math.random()}

On every response that nextjs sends so every request made will always make new response and not cache the data

Success true is just my message to tell the frontend that the mail is sent

I have tried this but not working for me. I am using brevo SMTP for sending mail to users which do not have their password set yet... It is working fine on local but on production it is not working... Also please do let me know if there is any way you know for debugging production code?

tbh for me i just kept pushing my changes wait for building and test

what i did is i made a test endpoint which will send email as soon as i get to it and the response would be the results of the endpoints to see the message ID (will be new each time you sent email)