OK, in this case, it's a very weird problem.
I've tried and I cannot replicate it on my environment. I don't think this is related with Energy Logserver database itself or an agent, as other pipelines are working properly. If database would experience any kind of disturbance, that would be seen across all indices and all pipelines.
I strongly suggest to reach to our official support for a online session, where we would be able to see the environment and identify the cause there. This can be related to performance, mapping, or many other elements. Upgrade to the latest version (7.5.0) can also help with this.