cancel
Showing results for 
Search instead for 
Did you mean: 

workflow hanging with Ready status

kavitha_c03
Explorer
0 Kudos

Hi,

We have a running workflow for years without issue with approvers across region. There was a change in the approvers list and a team took over the whole approval process. That is they started all the approval during a particular time . Once this started , randomly workflow started hanging ie 1 out of 10 wf is hanging.

it is hanging exactly in the background step where the method is having a commit statement.

What can be the reason ?

Thanks,

Shri

Accepted Solutions (1)

Accepted Solutions (1)

former_member185167
Active Contributor
0 Kudos

Hello,

It could it be locking. Any shortdumps in ST22?

Are you able to replicate the problem reliably?

regards

Rick Bakker / hanabi technology

kavitha_c03
Explorer
0 Kudos

Hi Rick,

Thanks for the reply. There is no shortdump at that time or during that hr itself.

We are not able to replicate in test systems. In production it is consistent.

that is in a day at least 1 out of 10  is hanging. sometimes the frequency increases.

Thanks,

Shri

former_member185167
Active Contributor
0 Kudos

Hello,

I just realized you said it's hanging in a background step in Ready status. Are you sure?

That's not a normal status for background jobs. Make sure it really is still background.

regards

Rick Bakker

kavitha_c03
Explorer
0 Kudos

Hi Rick,

It is a background step after a dialog step.  Background step  is in Ready status.

When I check the logs,the step history shows some tRFC entries and it stops there.

For the successful ones there are some 3 steps after that tRFC step.

Can this help

Thanks,

Shri

former_member185167
Active Contributor
0 Kudos

Could you please show a screenshot of the workflow log showing the background step in Ready state.

kavitha_c03
Explorer
0 Kudos

Something like ths

To add there is no SM58 lock or SM12 lock nor ST22 dump during that time

anjan_paul
Active Contributor
0 Kudos

Hi,

  Check in the ST22 from the time the its created upto 30 min there is any dump for deadlock . Share the screenshot for ST22 upto 30min .

kavitha_c03
Explorer
0 Kudos

Hi Anjan,

Thanks. There is no dump at all at anytime at all for WF-BATCH or for any other users during those times.

Thanks Shri

kavitha_c03
Explorer
0 Kudos

Will this report RSWWERRE  help?

anjan_paul
Active Contributor
0 Kudos

Hi,

  check in swu3, execute the schedule background job for workitem with error. and what is the Repeat  counter maintain there. I think it is not very high

kavitha_c03
Explorer
0 Kudos

Hi Anjan,

we have not maintained that at all. it is in red. I think that the report RSWWERRE  is linked to that step. now if we run/schedule it ,will it cause a issue becoz there are many other workflows also running in production

Thanks

anjan_paul
Active Contributor
0 Kudos

Hi,

  You should schedule this report RSWWERRE. It will not cause you any provlem. Thats the reason that background  step havin error is in Ready state. If you run it then you can find out what is the error using dump or application log

w

kavitha_c03
Explorer
0 Kudos

Hi,

Is it possible to do this customization for the workflows going forward.

There are many workflows running for years and there are some 2000 hanging workitems  for around 8 years.

so if we run this , it will re initiate all these 2000 hanging workitem , which was changed manually already as the workflow was hanging very rarely before.it may result in other data inconsistency.

Can this also be handled somehow?

Thanks,Shri

anjan_paul
Active Contributor
0 Kudos

Hi,

  It is very much surprised you have 8 years old workflow. I feel if you run it then all the hanging workitem will go to error state . If some workitem proceed successfully then you have to find out which workitem going to some agent and functionlity also. And you have to decide what to do.

former_member185167
Active Contributor
0 Kudos

Hello,

I suppose you could try creating a ZRSWWERRE which will only do new workitems but you should try turning it on in SWU3 in your Test system to see what happens. Why was that job not running?

regards

Rick Bakker / hanabi technology

pokrakam
Active Contributor
0 Kudos

I suppose the obvious answer is to cancel those workflows you don't want to restart.

This job is a really fundamental to WF operations, you should really sort this out and get it running.

kavitha_c03
Explorer
0 Kudos

Hi All,

Thanks for all your help.

I am not sure why this job wasnt run before. But we will change it. We will try to cancel those hanging workflows if possible and then try this job or go with the z option . We will analyse both these options Thanks, Shri

Answers (0)