incomplete-app-router-transaction
Unanswered
Milkfish posted this in #help-forum
MilkfishOP
Has anyone seen this error before, and can advise what it means?
My app threw the error during a server action which got caught on Sentry, but I can't seem to recreate it in production or localhost!
My app threw the error during a server action which got caught on Sentry, but I can't seem to recreate it in production or localhost!
26 Replies
I assume you use
redirect() in your server actions, right? @MilkfishMilkfishOP
Thats right, there is a redirect
yeah, so
redirect internally throws an errorthat's why you have tones of logs in sentry
MilkfishOP
The odd part is, an error was only ever thrown once - and it actually redirected the user to the nextjs error page
I've tried my best to track down the cause, but alas - so hoping to find out more details. Even searching for 'incomplete-app-router-transaction' in nextjs code base doesn't return anything
incomplete-app-router-transaction - what's this? error code?can you show me the codebase of your server action?
MilkfishOP
Nothing crazy, and I spent last night racking my brains!
hmm why don't you wrap your codebase with try catch to log errors?
but you shoudln't include
redirect@Milkfish Click to see attachment
can't you reproduce this error, btw?
MilkfishOP
The issue is I can't actually recreate the error
On prod, or dev
And watching the session replay - the user didn't do anything abnormal, they just pressed submit on the form
to trigger the action
@James4u `incomplete-app-router-transaction` - what's this? error code?
this is something used in the sentry not originally from error itself - so debugging this error code won't be much helpful
@Milkfish And watching the session replay - the user didn't do anything abnormal, they just pressed submit on the form
Prisma might be not responding at that point?
MilkfishOP
I thought maybe that too, but both Prisma and Inngest correctly recorded the transaction
It honestly seems like just the redirect failed
inngest codeblock is creating a record?
@Milkfish It honestly seems like just the redirect failed
I don't see any reason
redirect() gets failed - if it was failed due to slug mismatch it should fall into 404@James4u inngest codeblock is creating a record?
MilkfishOP
yep
looking at sentry again, the error is 'connection closed'