QueryException: Entity queries must explicitly set whether the query should be access checked or not.

@AlfTheCat,
I didn't find any issue in edit and save. There may be some other reason at your end.

@shailja179 thanks for the reply and yes, I think indeed there is another culprit. It looks like the entity_clone module breaks the message module. Even when not cloning any message entities, it still seems to break things.

I filed an issue there 🐛 Breaks the message module Active and am closing this one :)

I see the same issue even though I'm not using the entity clone module.
I don't think it's related to the entity clone module.
It happens when I try to delete messages.(/admin/config/message/message_delete_multiple)

stephen Verdant → made their first commit to this issue’s fork.

@erdm #4: I think message_delete_multiple is a separate bug not related to entity clone, see: Message delete multiple error: Entity queries must explicitly set ...access checked 🐛 Message delete multiple error: Entity queries must explicitly set ...access checked Fixed

Yes, you're right, it's another bug, but I just wanted to point out that I saw the same error even though I couldn't use the "entity clone module". This issue may not be related to the "entity clone" module.

This is a duplicate of 📌 Access checking must be explicitly specified on entity query Fixed