DocumentationCommerceTools

[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

ACSD-65254: Email notification not sent after updating customer email via updateCustomerEmail GraphQL mutation

Last update: Mon Jun 23 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACSD-65254 patch fixes the issue where email notifications weren’t sent to customers after updating their email addresses on their accounts using the updateCustomerEmail GraphQL mutation. This patch is available when the Quality Patches Tool (QPT) 1.1.65 is installed. The patch ID is ACSD-65254. Please note that this issue is scheduled to be fixed in Adobe Commerce 2.4.9.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.7-p1

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.4 - 2.4.7-p5
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

Issue

Email notifications were not sent to customers after updating their email addresses using the updateCustomerEmail GraphQL mutation.

Steps to reproduce:

  1. Create user using below mutation:

    code language-none 
    mutation {
    createCustomer(
        input: {
            firstname: "Test"
            lastname: "User"
            email: "test@test.com"
            password: "Admin@123"
            is_subscribed: true
        }
    ) {
        customer {
            created_at
        }
    }
}

  2. Generate a token for the previously created user and use it as a bearer token:

    code language-none 
    mutation {
generateCustomerToken(email: "test@test.com", password: "Admin@123") {
    token
}
}

  3. Try to update the email for the previously created user using the last created bearer token:

    code language-none 
    mutation {
    updateCustomerEmail(email: "test+updated@test.com", password: "Admin@123") {
        customer {
            email
        }
    }
}

Expected results:

Customers should receive email notifications after updating the email addresses on their accounts.

Actual results:

Only a subscription email is sent to the new address; the confirmation email for the email address change is not sent.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3