Invalid time value for field – – Elasticsearch Error How To Solve Related Issues

Invalid time value for field – – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “invalid time value for field -” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”invalid time value for field [{}] – [{}]”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (TIME_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
  if (token != XContentParser.Token.START_ARRAY) {
  try {
  timesSet.add(DayTimes.parse(parser; token));
  } catch (ElasticsearchParseException pe) {
  throw new ElasticsearchParseException("invalid time value for field [{}] - [{}]"; pe; currentFieldName; token);
  } else {
  while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
  try {
  timesSet.add(DayTimes.parse(parser; token));

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Getting a RangeError: Invalid Time Value when using React datepicker -views 5,857 ,score 6

Elasticsearch date format parsing error -views   5,508,score 1

Find Configuration Errors

Analyze Now