Order processing events defined in etc/frontend/events.xml won't work in production mode, works in development mode

[jakwinkler]

Preconditions and environment

• Magento version: 2.4.3-p1

Steps to reproduce

1. create a new module
2. add an event for the frontend related code part: etc/frontend/events.xml and add an observer

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">
    <event name="sales_model_service_quote_submit_success">
        <observer name="customer_event" instance="My\Module\Observer\OrderObserver" />
    </event>
</config>

or any event related to order processing / getting order data

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">
    <event name="checkout_submit_all_after">
        <observer name="customer_event" instance="My\Module\Observer\OrderObserver" />
    </event>
</config>

3. Log order data somewhere

/** @var Order|DataObject $order */ 
$order = $observer->getEvent()->getOrder();
if ($order) {
     // log order data anywhere, even with logger interface
     $this->logger->critical($order->getIncrementId());
}

• ENABLE PRODUCTION MODE *

Expected result

I can see the logged information in the log files

Actual result

Event is not fired at all, it is missed.

Additional information

This only happens in production mode, works fine in dev mode.
Moving events to etc/events.xml solves the problem, but I want my observer to work ONLY on the frontend part.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• 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]

Hi @qsolutions-pl. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[jakwinkler]

I'll just leave a note so the issue is not closed by stale-bot

[m2-assistant]

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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[engcom-November]

Hi @qsolutions-pl ,
Thank you for reporting. Verified the issue on Magento 2.4-develop branch but couldn't reproduce the issue.
Steps performed:
1. Create a custom module
2. Set mode developer
3. Add events.xml in etc/frontend
Its not getting called in developer and production mode. Because all orders related requests perform by REST API calls. So you need to add events.xml in etc webapi_rest directory or global inside etc/events.xml

Thank you.

[engcom-November]

Hi @qsolutions-pl ,
We are closing this issue as there has been no latest update on the same. Kndly reopen/create new issue if you are still facing any issues.
Thank you.

[hans-vereyken]

I'm a bit late to the party, but it's expected. Move your events.xml to the webapi_rest area described here:
#1581