Re: After publishing an updated node.js app to Heroku in our prod env. I'm not seeing any changes

After publishing an updated node.js app to Heroku in our prod env. I'm not seeing any changes

cneale
Visitor
3 0 0

After publishing an updated node.js app to Heroku in our prod env. I'm not seeing any changes in our Shopify production store. Our production store acts as if it is caching the previous version of the node.js app. I have confirmed that my newest changes are indeed in the code on Heroku but Shopify is totally ignoring them. I've tried swapping themes, making a minor edit to theme.liquid and that did not make a difference. Our sandbox store using the sandbox Heroku app works as expected. All I have done is deploy the code from Heroku sandbox to Heroku production. Any help would be greatly appreciated.

Replies 2 (2)

cneale
Visitor
3 0 0

Just update this and add a little more detail. Our node.js app is using webhooks to listen to Shopify more specifically orders/create. Our staging app has been working with no issues and our prod app has been working fine as well. I just made some enhancements to one our apps features and have not touched anything related to the code around the webhooks. After deploying to prod, out prod Shopify store is still running like it has in the past and but our prod Node.js app seems to be totally ignored. I've tried purging cache on Heroku and tried purging cache on Shopify with no luck. Does anyone have any ideas to what I might be able to try next?

cneale
Visitor
3 0 0

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?