Adding more to this… I have discovered that there is another legacy Ruby on Rails app hosted on Heroku as well that is taking president of the order processing “orders/create” web-hook. In our staging environment, configured the same way, the second app, Node.js app hosted on Heroku successfully hooks into the “orders/create” web-hook. The legacy Ruby app still needs to be running for our production app but can anyone point me in the right direction to attempt to make the Node.js be the app that gets the web-hook first or should both of them be able to work simultaneously?
Topic summary
Updated Node.js app deployed to Heroku production shows no changes in the Shopify production store; behavior appears cached or ignoring the new code despite confirming the deploy. Staging/sandbox works as expected.
Attempts made: swapping themes, editing theme.liquid, and purging caches on both Heroku and Shopify did not help.
Technical context: the app listens to Shopify webhooks (orders/create), i.e., HTTP callbacks triggered when an order is created. Recent enhancements did not modify webhook-related code.
Newest finding: a legacy Ruby on Rails app on Heroku production is receiving and processing the orders/create webhook, seemingly taking precedence, causing the Node.js app to be ignored. In staging, with similar configuration, the Node.js app successfully hooks into orders/create.
Open questions: how to configure Shopify/Heroku so the Node.js app is the primary recipient of the orders/create webhook in production, or whether both apps can process the webhook simultaneously without conflicts.
Status: unresolved; requesting guidance on webhook routing/priority and any further steps to ensure the Node.js app receives production webhooks.