N
Neon2y ago
ambitious-aqua

Persistent DuplicatedOperationError issues

Getting a lot of this when I first fire up our app for the day:
"Connection failed: {"errors":[{"errorType":"DuplicatedOperationError","message":"Duplicated operation with id 0fcfe9d7-afd7-46c6-bd80-3c2831381d89"}]}"
"Connection failed: {"errors":[{"errorType":"DuplicatedOperationError","message":"Duplicated operation with id 0fcfe9d7-afd7-46c6-bd80-3c2831381d89"}]}"
After a couple of page reloads, it stops. Should I be doing anything differently here? using fetchConnectionCache: true and using the non-pooled connection, via Lambda
15 Replies
plain-purple
plain-purple2y ago
What's your Lambda function timeout? I found that the default 3 seconds might not be enough with some databases from a cold start
ambitious-aqua
ambitious-aquaOP2y ago
like, a few minutes I don't think the default timeout is 3 seconds. should be 30, off the top of my head whoa, you're right. 3 seconds??!! that's nuts it used to be 30, back in the day 😄 ok, in our case I've set our timeout to 30 for all GraphQL resolvers
plain-purple
plain-purple2y ago
Yeah, I was surprised by that recently too. Fingers crossed it does the trick
ambitious-aqua
ambitious-aquaOP2y ago
yeah, def not related to Lambda timeout @Mahmoud any ideas? any recommendations?
plain-purple
plain-purple2y ago
My bad. Sorry for the misunderstanding!
ambitious-aqua
ambitious-aquaOP2y ago
no worries 🙂
plain-purple
plain-purple2y ago
I’m not familiar with Amplify ( seems to be what’s reporting the error based on googling), hopefully Mahmoud has an idea
ambitious-aqua
ambitious-aquaOP2y ago
still seeing this message, typically as the DB warms up
"Connection failed: {"errors":[{"errorType":"DuplicatedOperationError","message":"Duplicated operation with id 1ba4aaf0-b6c0-4168-b845-9aaf9a0ab889"}]}"
"Connection failed: {"errors":[{"errorType":"DuplicatedOperationError","message":"Duplicated operation with id 1ba4aaf0-b6c0-4168-b845-9aaf9a0ab889"}]}"
@Mahmoud has anything been changed/improved in recent iterations? should I still be using the non-pooled connection and be setting neonConfig.fetchConnectionCache = true?
adverse-sapphire
adverse-sapphire2y ago
Let me check with the team and get back to you
ambitious-aqua
ambitious-aquaOP2y ago
thank you, much appreciated!
adverse-sapphire
adverse-sapphire2y ago
@Sam Hulick btw are you using the latest version of the serverless driver?
ambitious-aqua
ambitious-aquaOP2y ago
@neondatabase/serverless 0.6.1
adverse-sapphire
adverse-sapphire2y ago
the latest version is 0.7.2. do you mind updating and letting me know if the issue persists?
ambitious-aqua
ambitious-aquaOP2y ago
ah! forgot to run --latest on the pnpm update. lemme do that issue is still happening
exotic-emerald
exotic-emerald2y ago
Hey @Sam Hulick , I'd be happy to jump on a call and see what's going on just to get a better understanding if that works. Early next week if we can't get it sorted by then? 🙂

Did you find this page helpful?