Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Elasticsearch 7.10 breaks Workflow Metrics in DXP 7.3 GA1

Written By

Tibor Lipusz

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Environment

  • Liferay DXP 7.3 GA1
  • Elasticsearch 7.10+

Symptom

When Liferay DXP 7.3 is configured to connect to Elasticsearch 7.10, navigating to Applications Menu > Workflow > Metrics and selecting a workflow entry (like "Single Approver") generates the errors below in the console. The functional impact consists of various elements within Workflow Metrics failing to load depending on what the user is doing.

Workaround

Stay on Elasticsearch 7.9.x.

Resolution

This is a regression introduced in Elasticsearch 7.10.0. Liferay reported this to Elastic Support and they created https://github.com/elastic/elasticsearch/issues/66057. However, later Elastic confirmed that it is not going to be addressed. Elasticsearch 7 will continue to throw an error on <Long, Object and will only accept <String, Object> moving forward so they won't be lenient.

Liferay's Workflow team has fixed it in LPS-124213, included in DXP 7.3 FP1/SP1.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?