[Task Management] Redwood_TM_Escalation is running indefinitely

Symptoms

Redwood_TM_Escalation is running indefinitely and no escalation are being done.

The output stdout.log will show regularly following message:

- Trying to persist
- JCS-102011: Out-value Out Value String cannot be set on Parameter DeadlineMissed for process xxxx because its process is final
- Unable to persist

Cause

Redwood_TM_Escalation will go into an infinite loop when Task which have miss there deadline are in inconsistent state, for example the task is in end status while the UserMesaggeJob still in console state.

Steps to reproduce:

1. Duplicate Redwood_TM_ManualTask (ie:  Redwood_TM_ManualTask_t109753
2. Go to Orchestrator and create a new ProcessList (PL_t109753)
3. set following parameter

   • deadline: set it to 01:00.

   • Executing Person: Set it for your current user.

   • Subprocess: Use a test subprocess, such as a named test.

   • working hours: choose the System_Week_WorkingHours calendar.

4. Submit the processLits
5. See that Redwood_TM_ManualTask_t109753 is in waiting and sub usermessage process is in console
6. Submit System_ForceJobStatusUnknown for Redwood_TM_ManualTask_t109753 process
7. Submit Redwood_TM_Escalation
8. See that it now run indefinitely

Workaround

You can kill Redwood_TM_Escalation and then create a report definition with below query.
Please review process shown in ConsoleJob column to have them set in end status.
Once the report does not show any result Redwood_TM_Escalation, should be able to execute as expected.

Query:

Select pj.JobId as ParenJobId, pj.Status as ParentJobStatus, o.Job as ConsoleJob from JobDatum o, Job j , Job pj
where o.Job = j.UniqueId
and j.ParentJob = pj.UniqueId
and o.DatumDefinition in ( select dd.UniqueId from DatumDefinition dd where dd.Name = 'Redwood_TM_WorkflowType')
and o.ValueNumber is not null
and o.ValueDateTimeZone is not null
and o.ValueDateTimeZone <= NOW()
and j.Status = 'O'
and pj.Status not in ('W')

Affected version

TaskManagement

Resolution

This issue is fix in version 2025.2.0.0

Reference 

ROSO-15712