Something went wrong with processing current custom view and filters have been reset to its original state. Please edit filters then click apply.

[abdullahzeb11]

Preconditions and environment

• Magento version
• Anything else that would help a developer reproduce the bug

Steps to reproduce

;magento 2.4.5 from sales> order page is loading and this error comes Something went wrong with processing current custom view and filters have been reset to its original state. Please edit filters then click apply.

Expected result

Something went wrong with processing current custom view and filters have been reset to its original state. Please edit filters then click apply.

Actual result

Something went wrong with processing current custom view and filters have been reset to its original state. Please edit filters then click apply.
and i cant see my orders in sales>order page

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

[m2-assistant]

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

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

[m2-assistant]

Hi @engcom-Bravo. 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-Bravo]

Hi @abdullahzeb11,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Could you please refer this solution :

• Please check "catalog_product_entity" table in the database for any sku 's having NULL value and update them:
  UPDATE catalog_product_entity SET sku='' WHERE sku IS NULL;
• Check if the user is having very restricted Access to the magento backend and grant users access to the product catalog / orders that may fix this issue.
• Run the query: TRUNCATE ui_bookmark; this will reset the grid back to it's default and stop the infinite load.

Kindly recheck the issue on Magento 2.4-develop branch and elaborate steps to reproduce if the issue is still reproducible.

Thank you.