shop/update webhook issue

Happening since yesterday and we use Gadgets default shop/update action so I am confident this error isnt on our end
No description
7 Replies
forslunds
forslunds3w ago
Seems like a loop, are you sure you are not doing anything at all on that action?
safwan
safwanOP3w ago
yeah pretty sure nothing on my end
Smelvin
Smelvin3w ago
Hi Safwan, Is this your whatflow app? I have investigated your shopify update action and it is not default, there are functions within it that are running every time a shop has any update
Chocci_Milk
Chocci_Milk3w ago
Is there anywhere in your application where you might be making calls to update the shopifyShop record? Have you looked to see if there's a particular shop thats making all the requests?
safwan
safwanOP3w ago
Based on the trace I already examined for this same trace ID, I can explain this log entry: What this log entry means: This message indicates that an error occurred while executing the run function of a Gadget action, and the system is automatically retrying the operation. Context from the trace: This happened during the processing of a Shopify shop/update webhook from the shop "UZAIR TRADERS". Here are the key details: The sequence: Shopify webhook received: A shop update webhook came in Background action started: Gadget began processing this webhook to update shop information Network error in run function: About 14 minutes into processing, the run function encountered a network error Automatic retry: The system logged this message and automatically retried the operation The specific error details: Error type: CombinedError: [Network] undefined Network error code: 1006 (WebSocket abnormal closure) Phase: This happened during the run phase of the action Action ID: shopify-webhook-74256580835-shop/update-b8b9dd6c-6301-483e-bc43-cc7dba26d60a Why this happens: The run function error was caused by: A WebSocket connection unexpectedly closing (error code 1006) Network instability between Gadget's execution environment and its internal GraphQL API This caused the database transaction to fail, leading to the rollback issues we saw earlier Gadget's automatic handling: Retry mechanism: Gadget automatically retries failed actions Background processing: Since this was a webhook, it's processed as a background action Error recovery: The system attempts to recover from transient network issues This is a transient infrastructure issue rather than a problem with your application code. Gadget's retry mechanism is designed to handle these types of temporary network failures automatically. No it wasnt any one shop happened to all almost. most of my logs were plagued with a familiar error for all stpres and when i asked the gadget ai assistant to exolain the issue this is what it told me: that's correct, it is also the default mantle identifier, haven't changed anything in that ever since i got into production around a year ago. My question is still the same, why is it that this suddenly started happening on 2nd august and continued until a day. Got fixed automatically yesterday. No changes pushed whatsoever. I am confident whatever happened wasn't our code base and up until now we have incurred 3300+ hours of request time on this action alone
Smelvin
Smelvin3w ago
Thank you for the information, we're actively looking into this
safwan
safwanOP3w ago
resolved

Did you find this page helpful?