transactionally enqueued action and non-transactionally enqueued action duplicates detected, discard
I see this error quite a bit in our logs and not sure exactly what it means. Can anyone help shed some light on it?
7 Replies
Hello,
Could you please share a traceId?
Yep,
0f3cdb56e03872db5f8577c93bbff8f2
is an exampleI'm not seeing the messages that you're seeing. Do you mind sharing the exact message on the log? Also, is this a sync?
Looking at some of the errors from this trace it looks like it might be OOM errors cause I'm seeing
ECONNRESET
errors
So I think there's more going on here than the issue that you're seeing
Or it might even be that the application is crashing because of other side closed
errors
Let me dig more to really figure out the issue
Ok, something is actually wrong with the trace you sent me so some of what I told you is incorrect. I'm seeing 2 apps logs for the same trace
Let me narrow it downI have seen that on a few traces recentlyh
and not sure why it is happening
they seem to be getting mixed together from multiple differenct processes
You're seeing the other application's logs? Thats extremely bad if thats the case
Sorry, not different applications that I have noticed. But it does seem to be multiple different jobs from different shops sometimes mixed into one trace id.
@airhorns
When it comes to the actual issues, there are a bunch of things that can be going on here.
- During the sync, you ran into an error that was encounter by the platform (Gateway timeouts, 504 errors)
-
Timeout awaiting 'connect' for 1500ms
: Getting rate limited by Shopify or Shopify generally having server issues
- [GraphQL] GGT_TRANSACTION_TIMEOUT: Can't commit a transaction after it has timed out
: Generally happens because you have action code that's running for too long (could be an action being held up by something down the line)
For the specific error you reported, I just found logs but gotta dig some more
I personally think that the log that you were seeing shouldn't have been exposed to you. Talking to the team about it/waiting on a response