Workflow Event delayed start

[justin_santhanam]

Dear all,

Wish you a happy new year! I would like to get some input on one of the issues I'm having with my current production environment. We have custom workflow built for Purchase Requisition. It's working all fine. But lately I have noticed once in a while some odd behaviour. The workflow is not starting immediately after the users release the requisition in ME54n. Most of the times it's immediately the workflow triggers,but few times I have noticed the  workflow only starts after 25-30 mins. There is no certain pattern. Sometime it's 15 mins sometime it's 30 mins. I checked the CDHDR/CDPOS and it says the req has been changed  for example 9:25 AM. But the workflow starts only at 9:55 AM (just an example). Where should I see to figure out why there was a delay in the process starting.

Appreciate all your assistance!

Thank you!

[AnggiM]

Hi, were you able to solve this case? The same thing is happening to me.

[Jocelyn_Dart · Accepted solution]

Hmmm... try checking SM58... they may have been stuck in the queue.

Also check SWEQADM - if the event queue is on (it should be!) then there may be some smoothing happening there.

And ask your basis team if there's any heavy usage going on... sometimes if the same dialog or background processes are being shared and someone floods it with a heavy batch job... your event may be just be waiting on system resources.

[justin_santhanam · Accepted solution]

Hello Jocelyn,

Thanks for your reply. This is sporadic occurrence. Is it possible for me to go back on that time frame and see what happened at that point?

Thanks.

[Jocelyn_Dart · Accepted solution]

Only if the event trace is turned on at the time - transaction SWELS.  That generally shouldn't be on for too long in production.. e.g. you might want to just turn it on for a few days.  SM58 also is about looking at it when the problem occurs.

[justin_santhanam · Accepted solution]

Okay, thank you! I know for sure SWELS is not turned on. But you are correct I could turn it on just for this BOR object and see what's happening there and leave it for some time. Thank you so much for your suggestion. I'll give a try, hopefully will catch something

Thanks!

[former_member201570]

Hi,

Check in eventqueue ( T-code : SWEQADM ) regarding any events error / processing / still to be delivered.

Regards,

Shamsudheen