Could not parse trigger event for for watch . unexpected token – Elasticsearch Error How To Solve Related Issues



Could not parse trigger event for for watch . unexpected token – 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 “could not parse trigger event for for watch . unexpected token” 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”could not parse trigger event for [{}] for watch [{}]. unexpected token [{}]”classname  is ScheduleTriggerEvent.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (ElasticsearchParseException pe) {
  throw new ElasticsearchParseException("could not parse [{}] trigger event for [{}] for watch [{}]. failed to parse " +
  "date field [{}]"; pe; ScheduleTriggerEngine.TYPE; context; watchId; currentFieldName);
  }
  }else {
  throw new ElasticsearchParseException("could not parse trigger event for [{}] for watch [{}]. unexpected token [{}]";
  context; watchId; token);
  }
  }
 
  // should never be; it's fully controlled internally (not coming from the user)

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 uncaught syntaxerror unexpected token U JSON -views 355,482 ,score 295

SyntaxError: Unexpected token o in JSON at position 1 -views   325,673,score 125



Find Configuration Errors

Analyze Now