Background Workflow steps taking many hours to execute

[Carolyn A Fuller]

Rick,

RSWWERRE is scheduled to run every hour and half:

14:10:05
15:40:05
17:10:05

The step in question was just attempting to send email. What errors could have been encountered that RSWWERRE would have cleared up? Is there anyway for us to trace what the errors are?

Thank you so much for your help.

Carolyn

On Nov 12, 2010, at 6:11 PM, Rick Bakker wrote:

Carolyn,

You can usually tell from the step history that there's been a
temporary error (e.g. locking) by the presence of yellow triangles.

I don't see them here but note that it does have RSWWERRE in there -
that's the workflow error job that would resolve temporary errors.
Usually it tries every 20 mins for 3 times = the 1 hour delay you saw.
Look in SM37 to see how often that job runs.

regards
Rick Bakker
hanabi technology

On Sat, Nov 13, 2010 at 10:04 AM, Carolyn A Fuller <fuller at mit.edu<mailto:fuller at mit.edu>> wrote:
Rick,
I don't see anything in the step history that indicates errors. I'm
attaching a snap shot of the step history. Am I missing something?
Carolyn
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug


---

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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20101112/48e55248/attachment.htm