-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such entity with customerId on Magnto 2.4.7-p3 #39489
Comments
Hi @jayantakr1. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
This in itself is not a bug, you need to set this particular indexer to "Update on Save", which will make it green again. This was changed over here: #34557
This might be a bug, but it would help significantly if you can figure out how you're triggering it. |
I also observed this error in the log file on version 2.4.5, but I’m not sure what is causing the issue. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @jayantakr1 , Thanks for your reporting and collaboration. Steps to reproduce: Issue 2 - After Magento 2 version upgrade to latest version stil I am getting "No such entity with customerId". Thanks. |
What testing stpes do you need ? After Magenot 2 version upgrade customer grid indexing getting Update By Scedule red color , I think indexing not working. |
@jayantakr1: please re-read my previous comment. Also, this issue about "no such entity with customerId" is NOT related to the customer grid indexer. |
Preconditions and environment
Magento 2.4.7-p3
I have run indexing multiple time but not resolved. It's a Magento 2.4.7-p3 issue.
Steps to reproduce
Magento 2.4.7-p3
I have run indexing multiple time but not resolved. It's a Magento 2.4.7-p3 issue.
Expected result
No such entity with customerId". error have to resolved. Any one can help m eon this issue.
Actual result
No such entity with customerId". error on 2.4.7-p3
Additional information
No response
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: