Skip to content
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

Open
5 tasks done
jayantakr1 opened this issue Dec 17, 2024 · 5 comments
Open
5 tasks done

No such entity with customerId on Magnto 2.4.7-p3 #39489

jayantakr1 opened this issue Dec 17, 2024 · 5 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.

Comments

@jayantakr1
Copy link

Preconditions and environment

Magento 2.4.7-p3

  1. After Magento 2 version upgrade to latest version stil I am getting "No such entity with customerId".
  2. Customer Grid indexing "Update By scedule" always showing red.
    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

  1. After Magento 2 version upgrade to latest version stil I am getting "No such entity with customerId".
  2. Customer Grid indexing "Update By scedule" always showing red.
    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

  • 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”.
Copy link

m2-assistant bot commented Dec 17, 2024

Hi @jayantakr1. 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.


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.

@hostep
Copy link
Contributor

hostep commented Dec 17, 2024

Customer Grid indexing "Update By scedule" always showing red.
I have run indexing multiple time but not resolved. It's a Magento 2.4.7-p3 issue.

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

After Magento 2 version upgrade to latest version stil I am getting "No such entity with customerId".

This might be a bug, but it would help significantly if you can figure out how you're triggering it.

@Mohamed-Asar
Copy link
Contributor

I also observed this error in the log file on version 2.4.5, but I’m not sure what is causing the issue.

@engcom-Delta engcom-Delta self-assigned this Dec 18, 2024
Copy link

m2-assistant bot commented Dec 18, 2024

Hi @engcom-Delta. 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).
  • 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- 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-Delta
Copy link
Contributor

Hi @jayantakr1 ,

Thanks for your reporting and collaboration.
We have verified the issue in 2.4.7-p3 instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce:
Issue 1 - Customer Grid indexing "Update By scedule" always showing red.
As mentioned by @hostep, Issue resolves when we change Customer Grid Mode to "Update on save"
Before
update by schedule
After
image

Issue 2 - After Magento 2 version upgrade to latest version stil I am getting "No such entity with customerId".
Can you please provide more testing steps as we are unable to view this error in log file.

Thanks.

@engcom-Delta engcom-Delta added Issue: needs update Additional information is require, waiting for response and removed Issue: ready for confirmation labels Dec 18, 2024
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

5 participants