cancel
Showing results for 
Search instead for 
Did you mean: 

Job hangs in Running status even if the precondition expression evaluates to False

Former Member
0 Kudos

We have a Job Chain with the following configuration & scheduling


JOB CHAIN     (Scheduled every 30 mins round the clock)

STEP 01

STEP 02     (Precondition using Time window to run only 4 specific times of the day)


Step 02 precondition expression when evaluates to FALSE, not always but 5-10% of the time, the step stuck in "Running" state instead of final status as "Skipped"


I would appreciate if anyone can provide me any insight of this issue


Let me know if you need any additional details.


Thanks,

Bhushan

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks Nanda & HP for taking time and replying to the issue. Here are the details that you requested:

Build - M33.85-65736

Precondition is based on TimeWindow = <TW Name>, TimeWindow Status = Open & Time Zone specified

When I say 5-10% time, yes, rest of the time it works as expected and the job gets skipped. When the Precondition evaluates to TRUE it 100% does the job and works good. Problem is only when the condition evaluates to FALSE

Time Window is open for 29 mins.

STEP 02 is supposed to run at 2 PM, So Time Window will be open from 2:00:00 PM and closes at 2:29:01 PM to give enough time for STEP 01 to complete since Job Chain is scheduled to run every 30 mins (12, 12:30, 1, 1:30 and so on)

Similarly for other three instances for that day.

At time point I dont have the job which shows STEP 02 in "Running Status" where it should have been skipped since we do not keep jobs later than 20 instances

About time window, I already explained it above but below is the screen shot of opens at:

Thanks,

Bhushan

nanda_kumar21
Active Contributor
0 Kudos

Is there any chance, during those 5-10% you put that job/job chain in hold prior to its execution?

thanks

Nanda

Former Member
0 Kudos

No

nanda_kumar21
Active Contributor
0 Kudos

There is bug that was fixed in M33.104 build, that sometimes when a job chain was placed on 'hold' the pre-condition check for that job didn't fire.

Is the time zone of following items same? Just to confirm we are not missing anything.

  • Time Window
  • Queue
  • Job schedule

The job is not supposed to start if the pre-condition is False. I would raise an SAP OSS, since this might be a bug.

Thanks

Nanda

Former Member
0 Kudos

Time Zone for TW, Queue & Job Schedule are in same time zone.

Thanks !

h_carpenter
Active Contributor
0 Kudos

Hi Bushan,

I think we should wait for the next "failure", then you need to check if the start time of step 2 or the job was at a time when the time window was open, it has to be or we have a bug.

Regards,

HP

Former Member
0 Kudos

Yeah. Thanks both for drilling this down further !

h_carpenter
Active Contributor
0 Kudos

Hi Bhushan,

Could you please let me know when the time window is open ? is it open for more than 30 minutes at a time?

You can check this on the 'Opens At' tab of the time window.

Pre-conditions and time windows are binary, they are true/open or false/closed. I have never witnessed anything like this and suspect there might be something wrong with your time window.

Could you please provide us with screenshots of the job that was running when it should not have been and then a screenshot of the 'Opens At' tab of the time window for the time the job that was not supposed to start started.

Regards,

HP

nanda_kumar21
Active Contributor
0 Kudos

Hey Bhushan,

What is your CPS build version?

What is the exact pre-condition? you mentioned 5-10% of the time, so the rest of the time the status is "skipped"?

Its either a bug or the pre-condition evaluation may be TRUE for a fraction of time when it is being calculated.

If it's an old build, it may be a bug.If you search for your build version in the SAP notes, you will get the list of bug fixes done in the build next to your current build. That is good starting point if you think it is a bug.

Thanks

Nanda