You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had the same error minutes ago. Restarting the nodeJs-Service / Docker-Container fixed it for me.
May there an issue like: indexing on service start took too long, so that redis-om thinks it's not there?
[EDIT: still happens almost everytime I start my services. @guyroyse may you please have a look?]
The issue at our end (@MR4online, same company) was, that the index was overwritten by another service at startup. That in the end some fields were missing on the used index.
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
I don't see what's wrong with this simple query.
Schema
Query
Result
[ErrorReply: Property
lastMatchAt
not loaded nor in schema]The text was updated successfully, but these errors were encountered: