Magento 2.4.2 Uncached After Placing Order

[hasnatme]

Preconditions (*)

1. Magento 2.4.2 (CE)
2. Varnish Cache or FPC

Steps to reproduce (*)

1. Place order with any products from any category as customer.
2. Place order from admin panel with any products from any category.

Expected result (*)

1. Magento should purge cache for varnish only for the product by tag. And rest cache should remain intact.

Actual result (*)

1. However Magento registering full varnish cache to be purged and the whole store becoming unchached again. As a result slow user experience again and again as long as customers kept ordering.
2. Without placing any orders or changing anything, no cache is being purged until varnish TTL expires.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [x] 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[bot]]

Hi @hasnatme. Thank you for your report. To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[mrtuvn]

Seem unclear information or miss evidence Can you provide more details in the case varnish used which varnish version that you used + vcl config please share? Problem can reproduce in vanila clean installation 2.4.2 or reproduce only happen in your working instance Case 1 Both enabled varnish + FPC Case 2 Enabled Varnish Disabled FPC Case 3 Disabled Varnish Enabled FPC

As i remembered in checkout page FPC will not available (non-cache) by default and varnish will bypassed too

[hasnatme]

Hello,

This is my website www.banglashoppers.com you can check yourself by placing an order, you do not need to pay as we have cash on delivery system. My Hosting is cloudways.com. Please note, it is doing after couple of min, not instantly.

Using latest 2.4.2 CE with FPC and Varnish-6.0.7 revision 525d371e3ea0e0c38edd7baf0f80dc226560f26e

[rvanwilgen]

Seems related to issue #30128

[mrtuvn]

Turn out after place order with some deduct amount products internal code do some stuff to resync and clear cache. Seem this relate

[mrtuvn]

@hasnatme Can you update more details? So you have stock Inventory used ?

[m2-assistant[bot]]

Hi @engcom-Lima. 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).

  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-Lima]

Hi @hasnatme,

This issue seems duplicate to #30128.

Can you please check and confirm if you are having same problems ? If yes, we can close this issue since 1 issue is already open and you can follow up other thread.

[engcom-Lima]

Hi @hasnatme,

This ticket is duplicate to #30128 hence we are closing this one. Please follow up on other issue for the update.