Workflow -> Stuck in status STARTED

[Michael Pokraka]

Event queue might help a little, or if simultaneity is the issue it may
even make it worse by collecting x events/minute and firing them off
together. How many work items/minute are generated around the time this
happens?
Either way, this possibly has a smell about it like a database update
issue. See if SM13 yields up any failed updates, or ask basis to check th=
e
system logs (SM12 if you're brave) around the time it happens. You didn't
mention whether SCOT told you that it sent the mails or not - I'd almost
guess not.
 
Something useful to do is to forward WF-BATCH's SAP mails to an internet
address as update failures would generate one of these.
 
Cheers
Mike
 
Scott, Jason J. wrote:
> SCOT is fine as well. Its is a normal background task which sends en
> email as part of its processing.
>
> I have noticed that when the error email is sent they are in quick
> succession - like a couple within 2 seconds of each other -> Could it b=
e
> that when workflow events on the same business object are raise very
> close to one another (few seconds) that the system gets into some sort
> of deadlock status??? Maybe using the event queue could help?
>
> Jason Scott
>
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Dart, Jocelyn
> Sent: Tuesday, 20 January 2004 11:54 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow -> Stuck in status STARTED
>
>
> Hi Jason,
> Short dumps can cause a background step to break - i.e. it doesn't
> terminate properly.
>
> If it's a send mail step, also check SCOT - see if your mail system has
> a problem. It may be trying to resend the same mail over and over.
>
> Also from SWI1 you can use the menu option to reexecute the background
> work item. Jocelyn
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Scott, Jason J.
> Sent: Tuesday,20 January 2004 2:48 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow -> Stuck in status STARTED
>
>
> Thanks for the reply Jocelyn.
>
> I've checked both. SM58 is empty. And I have 1 short dump under WF-BATC=
H
> something to do with an assign statement crashing in one of the workflo=
w
> function modules - however there is only one of these - yet we've been
> getting lots of these error emails???
>
> If I look in the workflow log it has only one step which internally
> calls a send mail function. The log shows this as "green" - background
> workitem created. Then it follows it up with a line that says
> SWW_WI_ERROR_SEND_S which also has a green light?!?!
>
> Thankyou,
>
> Jason Scott
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Dart, Jocelyn
> Sent: Tuesday, 20 January 2004 11:43 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow -> Stuck in status STARTED
>
>
> Jason,
> Check if there are any messages appearing in transaction SM58 and if yo=
u
> have any short dumps for WF-BATCH. Regards, Jocelyn.
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Scott, Jason J.
> Sent: Tuesday,20 January 2004 2:11 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Workflow -> Stuck in status STARTED
>
>
> We are getting allot or emails to the workflow administrator stating
> that the workitem is stuck in status "STARTED" and that a correction
> measure needs to be initiated???
>
> See below for example.
>
> Has anyone seen these error messages before? If you check the workflow
> log it is all green - i.e. no errors are reports. The workflow diagnosi=
s
> transactions cannot find any problems either.
>
> We don't get the problems in DEV and TST systems, only PRD.
>
> Any help would be most appreciated.
>
> Thankyou,
>
> Jason Scott.
>
> Work item 000001355506 in status STARTED
>
> The work item "Email Building Security" (ID 000001355506) of type B has
> the status STARTED. Initiate a correction measure so that the respectiv=
e
> workflow (ID
> 000001355505) can be continued.
>
>