I'm experiencing the same issue on production environment with a site that runs on Episerver.CMS.Core 11.11.2.
Please advice what can be done to avoid this.
Am seeing the same in cms.core.11.14.0
Looks like it's a bug, according to Quan Mai.
It doesn't contain the bug Id though, so it will be a bit of a sport to track when is it going to be released, but still moving forward. All the best!
The bug is CMS-15434, which is accepted by the CMS UI team, but is not made public.
Note that the bug will make it easier to diagnose the problem, not fix it
Any update on this bug? It's bloating our log something fierce. Yesterdeay alone we had 92,966 of these entries.
If you upgrade to at least CMS UI 11.23.7, the log now contains the whole stacktrace which would make easier to understand what is wrong
Are there any common causes we can look at before upgrading to 11.23.7? I'm concerned about log size and performance when we include a stack trace on an issue happening nearly 100,000 times a day.
Unfortunately, production is the only tier we see this error in.
After upgrade to 11.13, we are seing these in the error log. They show up sporadically and then in long series of repetition of same error.
I didn't find anything wrong. And noone uses projects functionality, so basically there are no workflows in use. Also I tried to run Episerver notifications scheduled job, but it reports 0 messages to process and no errors are logged at the time.
Is this related to some missing configuration, or any ideas?