SWF_RUN 611 Execution Interupted

[Mike Pokraka]

G'Day Mark,

Can you play around with RFC destinations or event queuing to direct all
of these workflow triggers onto one app server at a time? Had similar
problems in the past which originated from a rogue app server which was
either misconfigured or just needed a reboot (can't remember any more
details than that).

Cheers,
Mike



On Thu, March 25, 2010 10:31 am, Mark Pyc wrote:
> G'day Joc, thanks for the response!
>
> Sorry, my bad. I meant to say SWWWIHEAD and no it's not it in there.
>
> The Step History at flow level shows:
>      Start Event Received
>      (Sub)workflow created
>      Workflow started
>
> All show No Errors.
>
> What we do have that complicates things is a Workitem Exit on the
> first step which writes to a Custom History Table. This code has
> executed and recorded the Workitem creation. So the WF invoked, the
> Worktiem was generated to some level because the Exit code ran, but
> then something failed which didn't seem to leave any trace of the
> error and didn't roll back all DB updates.
>
> We don't really need the Custom History for this task so we are
> removing this Exit to take it out of the equation. Having said that
> this Exit is used on almost all Dialog tasks and has been live and
> stable on other Workflow for 2 years.
>
> Also, this Workflow originally had 'Block Errors' when it went live in
> Jan which caused it to misbehave. This was then corrected within a
> week or 2.
>
> Without having a custom ABAP in Prod to help it's quite an onorous
> task to analyse which Flow instances worked and which failed, but what
> seems to be a pattern is that it fails for a period of time and then
> works for a period of time (a few hours of each). A theory floating
> around is that the issue is to do with system load, but no real theory
> about how system load would produce what we are seeing???
>
> Any advice from anyone on how to dig a little deeper?
>
> Thanks,
> Mark
>
>
> On 24 March 2010 21:28, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:
>> Mark,
>> Did you check if the  child WI was in SWWIHEAD?
>>
>> Agree it's weird. Anything in the Step History section at the flow
>> level? If it's the rule termination it should have shown up there ...
>>
>> Rgds,
>> Jocelyn
>>
>> ________________________________________
>> From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of
>> Mark Pyc [mark.pyc at gmail.com]
>> Sent: Thursday, 25 March 2010 4:21 AM
>> To: WUG
>> Subject: SWF_RUN 611 Execution Interupted
>>
>> G'day Wuggers,
>>
>> It's been a long time! Hope you're all well.
>>
>> I have a situation in an ECC6 / 7.00 system where an IDOC error
>> handling WF is sporadically failing in a very odd way.
>>
>> The WF History shows error SWF_RUN 611 Execution Interupted at the Flow
>> level.
>> The first step is listed with a Workitem ID / Step Number / Creation
>> timestamp but no other info (No WI Text, No Created By)
>> That first step Workitem ID does not really exist! It's not in
>> SWWUSERWI. It can't be displayed with SWI1.
>>
>> Normally when I see "Execution Interupted" I expect to see an ST22
>> short dump or something in SM21 System Log, but there is nothing.
>>
>> It seems very odd that the WF Log is written to with a Workitem ID,
>> but there is no other trace of it in the system, and no logged
>> failures that I can find.
>>
>> This first step is a Dialog task based on IDOCAPPL.INPUTFOREGROUND and
>> uses a copy of standard Rule 30000013 (copy has "Terminate if no
>> Result" selected).
>>
>> If I use SWUE and raise the same event for the same instance the
>> Workflow processes correcty. This suggests to me that there may be a
>> timing issue where the WF is triggering before the IDOC is fully saved
>> to DB, but even if this is the case it doesn't explain why there isn't
>> any proper error capture and why the WF is left "In Process" with a
>> child WI logged but not actually created.
>>
>> I can't find any OSS notes / WUG or SDN Posts that really help.
>>
>> I and the 3 other WF consultants here are baffled. Any ideas?
>>
>> Have fun,
>> Mark
>> _______________________________________________
>> 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
>