Background Workflow steps taking many hours to execute

[Carolyn A Fuller]

Rick,

I have my personal workflow settings set to Technical View. And the logs are all indicating green lights and no errors. 

I am not sure what you mean by "Admin would have logged a re-executed every 20 mins." RSWERRE is scheduled for every 90 minutes. (Hopefully this will change by Monday morning.) But even with it scheduled for every 90 minutes I don't see a log indicating that anything re-executed. 

The workflow administrators do receive messages when any workflow errors occur but we have not received any messages from these delayed workflows. 

Carolyn

On Nov 13, 2010, at 12:14 PM, Sample, Rick wrote:

> one more thing, you should be able to see that in the log. 
> Go to the task in question, tech view, and see what the logs tell you.
> Admin would have logged a re-executed every 20mins. Errors should
> be sent to the admin as msg.
> 
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu
>> [mailto:sap-wug-bounces at mit.edu] On
>> Behalf Of Sample, Rick
>> Sent: Saturday, November 13, 2010 10:56
>> AM
>> To: SAP Workflow Users' Group
>> Subject: RE: Background Workflow steps
>> taking many hours to execute
>> 
>> I agree, need more info. Like, any recent
>> changes to code like a loop?
>> 
>> But, temp errors are default to 20mins. 20
>> 20 and 20 is around 60, depending on
>> start / finish of SWWERR job.
>> Note: in 4.6c, the default was 20mins for
>> the Temp Err, I believe that has changed
>> for ECC6 due to BPM. But we stuck to
>> 20mins.
>> 
>> So, if temp error, sounds like it was re-
>> attempting something until it finished.
>> *sounds* like it.
>> Check the Task BOR method for temp
>> exceptions.
>> 
>> Rick Sample
>> 
>> 
>>> -----Original Message-----
>>> From: sap-wug-bounces at mit.edu
>>> [mailto:sap-wug-bounces at mit.edu] On
>>> Behalf Of Jimmy Sun
>>> Sent: Saturday, November 13, 2010
>> 9:58 AM
>>> To: SAP Workflow Users' Group
>>> Subject: Re: Background Workflow
>> steps taking many hours to execute
>>> 
>>> Carolyn,
>>> If you can explain more detail of what is
>> the step doing, it will help
>>> to determine ther problem.
>>> 
>>> Jimmy Sun
>>> Senior Consultant
>>> On 11/12/10, Carolyn A Fuller
>>> <fuller at mit.edu> wrote:
>>>> Hi all,
>>>> 
>>>> Recently, my end users have started
>>> complaining about the performance
>>>> of some of their workflow background
>>> steps. They said that this has
>>>> just recently become a problem.
>>>> 
>>>> Today, I looked at the logs for one of
>> the
>>> excessively slow workflow
>>>> background steps and it indicated that
>>> the background step was created
>>>> at 14:37:49, then started and ended
>>> over an hour later at 15:40:06.
>>>> This step normally takes less than a
>>> second to execute.
>>>> 
>>>> What could cause the hour delay
>>> between when the step was created and
>>>> when the step actually started and
>>> ended?
>>>> 
>>>> The workflow in question is using XML
>>> persistence. I converted this
>>>> workflow to using XML persistence
>>> about a year and a half ago.
>>>> 
>>>> ---
>>>> 
>>>> Carolyn Fuller
>>>> 
>>>> Senior Analyst/ Programmer
>>>> 
>>>> Information Services and Technology
>>>> 
>>>> Massachusetts Institute of Technology
>>>> 
>>>> Room W92-210
>>>> 
>>>> Cambridge, MA 02139
>>>> 
>>>> (617) 253-6213
>>>> 
>>>> http://fuller.mit.edu/
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> 「Money is gone, nothing is
>>> gone.（失去了金錢，沒有失去什麼）；
>>>    Hope is gone, everything is
>>> 
>> gone.（失去了希望，就失去了全部）。」
>>> 
>>> 
>> __________________________________
>>> _____________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> 
>> http://mailman.mit.edu/mailman/listinfo/sap
>>> -wug
>> 
>> __________________________________
>> _____________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap
>> -wug
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug