observer.customer_register_success event emits null customer object from Magento Cloud

[leojlu88]

Preconditions and environment

Magento CLI 2.4.6-p5

Steps to reproduce

We followed the steps on this page https://developer.adobe.com/commerce/extensibility/events/configure-commerce/ to set up I/O Events. We subscribed and registered both observer.customer_register_success and observer.customer_save_commit_after events. observer.customer_save_commit_after is working fine, but observer.customer_register_success events has null for the customer object. Here is the paylaod: { "data": { "key": "xxx", "value": {}, "source": "xxx", "_metadata": { "commerceEdition": "Adobe Commerce", "commerceVersion": "2.4.6-p5", "eventsClientVersion": "1.7.0", "storeId": "1", "websiteId": "1", "storeGroupId": "1" } }, "id": "xxx", "source": "xx", "specversion": "1.0", "type": "com.adobe.commerce.observer.customer_register_success", "datacontenttype": "application/json", "time": "2024-06-02T07:47:04.256Z", "event_id": "xxx", "recipient_client_id": "xxx" }

We have the ie_events.xml in app/etc <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module-commerce-events-client/etc/io_events.xsd">

Expected result

customer object emitted from the observer.customer_register_success event should have customer entity_id

Actual result

customer object from the observer.customer_register_success event is null

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @leojlu88. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[m2-assistant[bot]]

Hi @engcom-Hotel. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[naomirobichaud]

@leojlu88 team is looking into this, thanks for reporting

[engcom-Hotel]

We are moving this issue On hold until further updates.

[ryanjcohen]

Hi @leojlu88, we've included a fix for this issue in commerce-eventing v1.8.0

[engcom-Hotel]

Thanks @ryanjcohen for the information. We are closing this issue.