When is an error not an error?

[Becker Stephan (extern)]

Hi Michael,
 
Think about it what you will, but if a method does not return an =
explicit exception, the behaviour that you see is all you get..
 
The only solution in my experience is explicit exception coding, plus a =
little report that finds abended workflows in production..
 
Hth,
Stephan
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]=20
Sent: Dienstag, 18. M=E4rz 2003 12:47
To: SAP-WUG at MITVMA.MIT.EDU
Subject: When is an error not an error?
 
Hi all,
I have a bit of a troublesome situation:
Two steps, a user decision followed by a background task.
User executes item, and bg task fails due to binging/object issues. The
problem itself is another topic, but the most troublesome part is that
the WF remains in status 'In Process'!
 
In more detail:
Decision step logs look normal, ending with 'WI processing complete';
status 'COMPLETED'.
The next step does not appear in the log, but a red light appears in =
the
tech log with a message. No subsequent steps, nada. The only 'In
process' item on the whole log is the WF itself.
SWI2_DIAG doesn't show this up, which is why it's worrying.
The error is due to an uninstantiated object (resulting from a document
without line items) "Object 0 does not exist", "Syntax error in
expression" etc. I've no problem solving these, but more concerned =
about
other WF's in production.
 
Any input appreciated.
Cheers
Mike