Closed
Description
Preconditions and environment
- Magento version 2.4-develop
Steps to reproduce
- Set develop mode: bin/magento deploy:mode:set developer
- Login customer
- Clear cache: bin/magento cache:clean
- Load homepage
- Reload homepage and check x-magento-cache-debug header
Expected result
need response with x-magento-cache-debug: HIT
Actual result
response with x-magento-cache-debug: MISS => page not load from cache in fpc
Additional information
No response
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”.
Metadata
Metadata
Assignees
Labels
Gate 3 Passed. Manual verification of the issue completed. Issue is confirmedOnce P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Indicates that Pull Request has been created to fix issueIndicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branch
Type
Projects
Status
Ready for Development
Activity
m2-assistant commentedon Jun 18, 2025
Hi @rogerdz. 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.
@magento I am working on this
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.
m2-assistant commentedon Jun 18, 2025
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: 👇
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branchDetails
- If the issue is reproducible on2.4-develop
branch, please, add the labelReproduced 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!
Issue: Confirmed
once verification is complete.engcom-November commentedon Jun 18, 2025
Hello @rogerdz ,
Thank You for your report and collabration.
We have reviewed the reported issue and attempted to reproduce it in the both latest 2.4-develop instances. However, we were unable to replicate the issue on our end. Please find the attached screenshot for the reference.
Step to Reproduce
As we followed the precondition and steps we didn't encounter any issue, Kindly reverify the issue once from your side and let us know if we may have missing anything.
Hence we marking this issue as "Needs Update"
Thank You again!
rogerdz commentedon Jun 18, 2025
Hi @engcom-November
Are you using build in fpc or varnish?
Please test with build-in fpc
engcom-November commentedon Jun 23, 2025
Hello @rogerdz ,
Thank you for the report and collaboration.
We have attempted to reproduce the issue and can confirm it is reproducible on our latest 2.4-develop branch. Please see the attached screenshot for reference.
Steps to Reproduce:
Following these preconditions and steps, we have encountered the issue.
Therefore, we are marking this issue as Confirmed.
Thank you again for your collaboration!
22 remaining items