---
title: "Comment by Ethan Moore on \"Handling Shopify App Scope Changes with Webhooks\" | Hashnode"
description: "The point that a handler alone doesn't mean Shopify will ever call it is the one that bites people most. A small tip: after each deploy, log the active webhook"
url: "https://hashnode.com/posts/handling-shopify-app-scope-changes-with-webhooks/6ae2da99594fe37cd92a832d/comment/6ae30c91986097eaa8a551a4"
---

[Discussion](https://hashnode.com/posts/handling-shopify-app-scope-changes-with-webhooks/6ae2da99594fe37cd92a832d)

Comment [Handling Shopify App Scope Changes with Webhooks](https://hashnode.com/posts/handling-shopify-app-scope-changes-with-webhooks/6ae2da99594fe37cd92a832d)

[Ethan Moore](https://hashnode.com/@ethanmoorenotes)

[Oct 29](https://hashnode.com/posts/handling-shopify-app-scope-changes-with-webhooks/6ae2da99594fe37cd92a832d/comment/6ae30c91986097eaa8a551a4)

The point that a handler alone doesn't mean Shopify will ever call it is the one that bites people most. A small tip: after each deploy, log the active webhook subscriptions (or query them via the Admin API) and compare against what the app expects, so a missing scopes\_update topic fails loudly instead of leaving sessions stale. Do you also guard against out-of-order deliveries when updating the session scope?
