Invalid HipChatAction TYPE action for watchId actionId – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when an invalid HipChatAction.TYPE is used in a Watcher action for a specific watchId/actionId in Elasticsearch. This could be due to a typo, incorrect formatting, or using a deprecated or non-existent action type. To resolve this issue, you should verify the action type used in your Watcher action. Make sure it is correctly spelled, properly formatted, and is a valid action type. If the error persists, check the Elasticsearch documentation for changes in the Watcher API, as the action type might have been deprecated or replaced.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” invalid [” + HipChatAction.TYPE + “] action for [” + watchId + “/” + actionId + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “invalid [” + HipChatAction.TYPE + “] action for [” + watchId + “/” + actionId + “] ” class name is IntegrationAccount.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  @Override
 public void validateParsedTemplate(String watchId; String actionId; HipChatMessage.Template template) throws SettingsException {
 if (template.rooms != null) {
 throw new ElasticsearchParseException("invalid [" + HipChatAction.TYPE + "] action for [" + watchId + "/" + actionId + "] " +
 "action. [" + name + "] hipchat account doesn't support custom rooms");
 }
 if (template.users != null) {
 throw new ElasticsearchParseException("invalid [" + HipChatAction.TYPE + "] action for [" + watchId + "/" + actionId + "] " +
 "action. [" + name + "] hipchat account doesn't support user private messages");

 

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?