Stuck Workflows

[Pokraka, Michael]

Here's an (ugly?) hack to restart stuck items:
Call function SWW_WI_STATUS_CHANGE_NEW and set it to status ERROR. Then find
it in SWI2_DIAG and restart it.
You could build something fancy with deadline monitoring that will set it to
an error status after x amount of time, allowing you to monitor and restart
them from SWI2_DIAG.
 
Of course it is advisable to investigate the TRFC further if this is a
regular occurrence - you might want to get your basis folks involved in it.
 
Cheers
Michael
 
 
-----Original Message-----
From: casdhir at att.net [mailto:casdhir at att.net]
Sent: 07 October 2002 18:10
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Stuck Workflows
 
 
Hi all,
 
I have a bunch of WF's stuck at a background step in the test client. When I
look at the technical log I get a message WL 321 WI could not be started
runtime error? The transactional RFC call starting the background step
failed ... Calling the background step can be delayed in cases of high
system
load. Not sure why its happening, All the config checked ok, its a working
Prod
wf which is being enhanced but no changes to the worflow in this step. Any
ideas and how to restart the WF's.
 
Thanks.
Chavi
 
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law.  If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy.   Thank you.
 
 =============================================================================