Using System_ForceUnknown in Redwood CPS

[Former Member]

Hi Redwood Experts,

Our Redwood CPS Production System is currently experiencing issues.

     1. Process Chains cannot reached status COMPLETED, It is stuck in WAITING  status eventhough it was already completed in SAP side.

         So our work around is to force the PCs status to unknown to reaclculate to its next scheduled run.

     2. Most of our Jobs got delayed.For example,  a job that runs usually before in every minute frequency, as of now they are running for more than 10Min or higher . We have more than 5000+ Jobs that are currently running in Redwood CPS

Upon Investigation, We found out that there are several Jobs that are stuck in Waiting status for more than a month/year,Those Jobs are commonly CCMS jobs, jobs that are generated by Process Chains. .

My Question is,

     1.     When we unknown the PARENT job, does the child job status will also be UNKNOWN?

     2.      if Yes, Why some of its child jobs stuck in non-final state?(waiting/running)

     3.     Do those non-final state jobs still used Redwood resources?

     4.      Is there any options that we can do to bring those non-final state jobs to final state ?

     5.      Can you suggest any useful actions in order to prevent this kind of issue ?

Thank you for your help !

Regards,

--------------

leo

[Former Member]

Hi Leo,

Here are the answers to your questions

     1.     When we unknown the PARENT job, does the child job status will also be UNKNOWN?

Yes child jobs which are running will go to Unknown status.

     2.      if Yes, Why some of its child jobs stuck in non-final state?(waiting/running)

This should not be the case just check after upgrade.

     3.     Do those non-final state jobs still used Redwood resources?

If they are in non final status yes they use Redwood resources

     4.      Is there any options that we can do to bring those non-final state jobs to final state ?

Try putting parent job of the non final status jobs.

     5.      Can you suggest any useful actions in order to prevent this kind of issue ?

We have option to put all the job under process server to unknown status at on go.

Use the process server parameter while submitting System_ForceUnknown

[former_member212336]

Hi,

We have a similar issue where a job got stuck in Held status. SAP recommended us to use the System_ForceUnknown (didn´t work) and to upgrade to M33.117 which should resolve this.

Kind regards,

Jonas