Legacy Knowledge Base
Published Sep. 10, 2025

Resolving Job Scheduler Stuck in "In Progress" Status

Written By

Daniel Martinez Cisneros

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.

Issue

The Job Scheduler log status remains stuck in "In Progress" after a server outage during a triggered job and can not be deleted.

Environment

  • Liferay DXP 7.4
  • Quarterly Release 2023.Q3

Resolution

To address the issue of the Job Scheduler log being stuck in "In Progress" status follow these steps:

1. Utilize the provided Groovy script to change the status of the DispatchLog entry:

import com.liferay.dispatch.model.DispatchLog;
import com.liferay.dispatch.service.DispatchLogLocalServiceUtil;

DispatchLog dispatch = DispatchLogLocalServiceUtil.getDispatchLog(${dispatcherLogId})
dispatch.setStatus(4) //Status error

com.liferay.dispatch.service.DispatchLogLocalServiceUtil.updateDispatchLog(dispatch)

Ensure you replace ${dispatcherLogId} with the appropriate value. This ID can be obtained via one of two options:

  • Option 1: Extract it from the URL by clicking on the "In Progress" job and Look for

    _com_liferay_dispatch_web_internal_portlet_DispatchPortlet_dispatchLogId=33701&_com_liferay_dispatch_web_internal_portlet_DispatchPortlet_dispatchTriggerId=3362

    in the URL.

  • Option 2: Query the dispatcherlog table where the status is pending:

    SELECT * FROM dispatchlog WHERE status = 1 AND endDate IS NULL;

2. After updating, you can choose to either delete it or retain it with the correct status

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base