<div>HI Mike,</div>
<div>Thanks for the reply. Just to make sure that I have been able to convey my issue correctly, I am adding the following things:</div>
<div> </div>
<div>1. I gave the first step as an example. This does not necessarily happen at the first step. This may happen at any step in the workflow(being stuck as ready status).</div>
<div> </div>
<div>2. This is happening across the entire workflow system in workflows developed for all modules.</div>
<div> </div>
<div> </div>
<div>Does this make the issue different or clearer?</div>
<div> </div>
<div>Thanks,</div>
<div>Ashish<br><br> </div>
<div><span class="gmail_quote">On 1/12/07, <b class="gmail_sendername">Mike Gambier</b> <<a href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Ashish,<br><br>If I were you I'd check the following things to start with:<br><br>1. Is this a new/amended step? If so, are there any temporary exceptions
<br>(e.g. database locks) being fed back? Check in tech log if it is on, or<br>failing that have a look in SWWWIRET to see if there are any clues there. If<br>you find you do have temporary exceptions make sure you activated the
<br>Workflow exception handling batch job SWWERRE to have another go at trying<br>the steps again (check in SWU3).<br><br>2. If you have changed anything on related to the WF definition or Business<br>Object related to the task that is appearing to stubbornly refuse to start
<br>(but it used to work fine), it's probably something in your code/environment<br>causing a feedback error. Syntax check your WF and code for errors, such as<br>Agent Determination missing on dialog steps elsehwere in the definition. Try
<br>generating the Business Object, make sure the WF you are triggering is<br>active on the right version and the event linkage looks right. Drop the<br>Workflow buffers using SWU_OBUF to be sure you are using the latest versions
<br>of everything, if in doubt, and try to trigger the same WF again using SWUE<br>maybe.<br><br>3. Check the data related to your 'stuck' steps. Are all of your WFs hanging<br>at this point or are some working OK? If the latter is true then your
<br>definition may be dodgy with regards to binding or logic and may need<br>revising. Normally this would error though rather than stall, but you never<br>know.<br><br>4. If you have changed the way the WF is triggered (perhaps a different
<br>event entirely or a new container binding) make sure the WF being kicked off<br>is receiving the new info properly. Perhaps your event raising code isn't<br>quite right now?<br><br>5. Check for dumps to see if WF-BATCH is complaining about something that
<br>might be related.<br><br>6. If this is the first step in your Workflow and you're using the Event<br>Queue check to see what kind of 'delay' you have between delivery jobs.<br>Sometimes events can take a while to come through because they have lots of
<br>competition with other events. Wouldn't explain why your first step appears<br>to be 'stuck' but it might explain why there's an apparent delay between<br>events and WFs starting.<br><br>7. Sometimes the triggering event is only partially delivered and the call
<br>to your next step ends up being parked temporarily as a tRFC entry in<br>ARFCSSTATE for destination WORKFLOW_LOCAL_100 if the aren't enough dialog<br>process for Workflow to get hold of at the time. Have a peak at the RFC
<br>queue to see if this is filling up.<br><br>Mike GT<br><br>>From: "Ashish Paranjpe" <<a href="mailto:aaparanjpe@gmail.com">aaparanjpe@gmail.com</a>><br>>Reply-To: "SAP Workflow Users' Group" <
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>>To: <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>>Subject: Workflow steps remaining in ready state for long<br>>Date: Fri, 12 Jan 2007 15:38:34 +0100
<br>><br>>Hi All,<br>>I am facing a very atypical issue which I will try and explain below:<br>><br>>When a workflow is triggered in the system, the first step of the workflow<br>>is a background step. Now Ideally, i would have expected this step to
<br>>change<br>>from "READY" state to "INPROCESS" within a fraction of a second. What<br>>happens with our workflows is that these steps continue to remain în<br>>"READY" state for 2-3 hrs. Please note that there is no deadline monitoring
<br>>active for these steps.<br>><br>>I have 2 questions based on this:<br>><br>>1. How does the workflow system function with regard to changing a step<br>>state?<br>>2. More important quaetion : Why is this above mentioned problem occurring
<br>>in our system? Is it something to do with system performance?<br>><br>><br>>I may have raised this question before, but could not get a proper solution<br>>to the issue.<br>><br>>Thanks in advance.
<br>><br>>Ashish<br><br><br>>_______________________________________________<br>>SAP-WUG mailing list<br>><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br>_________________________________________________________________<br>Communicate instantly! Use your Hotmail address to sign into Windows Live<br>Messenger now. <a href="http://get.live.com/messenger/overview">
http://get.live.com/messenger/overview</a><br><br><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br></blockquote></div><br>