Datafeed has been before running – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.15-7.15

Briefly, this error occurs when an Elasticsearch datafeed is stopped or paused before it has completed its run. This could be due to a manual stop, a system error, or a network issue. To resolve this, you can try restarting the datafeed. If the problem persists, check the system logs for any underlying issues that may be causing the datafeed to stop prematurely. Also, ensure that your network connection is stable. If the issue is due to a system error, you may need to debug the system or consult with a system administrator.

This guide will help you check for common problems that cause the log ” [{}] Datafeed has been {} before running ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] Datafeed has been {} before running” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } else {
          "[{}] Datafeed has been {} before running"; task.getDatafeedId();
            }; finishHandler


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?