When is an error not an error?

[Michael Pokraka]

Hmm, problem is that there _is_ an exception (red light in the log), and
the error happens in the binding - i.e. before any method execution.=20
The error itself is arbitrary, what does worry me is that a  binding=20
error can cause a WF to simply come to a silent stop whilst remaining 'in
process'....=20
Sure one can argue that the design needs to be robust enough to handle
it, but when you're working at a client who already has a whole bunch of
their own flows this is not always an option.
 
By the way, what would a little report look for in this case?? Other
than deadlines or trawling through the logs I can't see much of a
concrete option.
 
Thanks for the input,=20
Cheers
Mike
 
On Tue, Mar 18, 2003 at 01:51:41PM +0100, Becker Stephan (extern) wrote:
> Hi Michael,
>=20
> Think about it what you will, but if a method does not return an explic=
it exception, the behaviour that you see is all you get..
>=20
> The only solution in my experience is explicit exception coding, plus a=
 little report that finds abended workflows in production..
>=20
> Hth,
> Stephan
>=20
> -----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?
>=20
> 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'!
>=20
> 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 th=
e
> 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 abou=
t
> other WF's in production.
>=20
> Any input appreciated.
> Cheers
> Mike