GraphQL Edit Order Email not sending

[sethroster]

Hello, I am running into an issue where the customer email is not sending after editing an order using graphql orderEditCommit. I'm doing exactly what seems to have worked for others as described in this thread https://community.shopify.com/c/shopify-apis-and-sdks/notifying-customer-when-their-order-is-edited/.... The order is editing successfully with no errors except for the email is not being sent. Here's the API version were on and the applicable API scopes being used:

API Version: 2023-01
Access Scopes: 
"read_customers"
"read_orders"
"read_all_orders"
"read_products"
"read_fulfillments"
"read_shipping"
"read_price_rules"
"read_discounts"
"read_script_tags"
"write_customers"
"write_price_rules"
"write_discounts"
"write_script_tags"
"write_orders"
"write_order_edits"

Code:

mutation orderEditCommit($id: ID!) {
                    orderEditCommit(id: $id, notifyCustomer: true) {
                        order {
                            id
                        }
                        userErrors {
                            field
                            message
                        }
                    }
                }

[jamesdv]

I'm having this same issue.  Does someone know what the cause is?

[ShopifyDevSup]

Hi @sethroster,

Thanks for your post. When testing in a test store using the [GraphQL Order Editing] process and adding a variant to the order, the email template is getting sent out successfully after the orderEditCommit mutation is submitted when notifyCustomer is set to true.

So this may be a store specific issue. One thing to check is that the test customer is receiving emails for other regular actions from the store in case there's some configuration issue with the store's Sender Email address.

For direct assistance please reach out [to Partner Support using the email option] and select the 'App Development & API' topic, and include more details like what specific operations were being completed during the order edit, what store and app were involved, and a specific date/time/timezone in the past 7 days when the issue was encountered.

Thanks and hope you have a great day