Workflow occasionally doesn't exec next step + Error m essagi ng

Wed Nov 29 06:42:16 EST 2000

Mark,
That sounds exactly like what's happening here - I've seen it happen usually
towards the end of a batch of IDOC's. I'll have to monitor and see what
happens.
Thanks for your input.
Cheers
Michael

-----Original Message-----
From: Griffiths, Mark [mailto:mark.griffiths at sap.com]
Sent: 28 November 2000 11:37
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow occasionally doesn't exec next step + Error m
essagi ng

Is the first step in the workflow a background step? if so I have come
across a similar problem with other EDI processes I've built - basically the
first step gets scheduled before the system has time to run it (particularly
in high volume situations), so it doesn't run.

A solution:
Use the Requested Start deadline to delay the step for a while (one minute
should do) and the workflow will then pick it up and run it when scheduled.
Of course be aware when testing this that the deadline may take more than a
minute depending on the scheduling of the background job (minimum of 3
minutes).

This technique works for most background steps that appear to inexplicably
fail to start themselves in a process. Obviously if you are using a stand
alone standard task this approach won't work so you may need to include it
in multi-step 'shell'.

Regards

Mark

Mark Griffiths
Marketplace Technologies Team,
SAP UK

-----Original Message-----
From: Michael Pokraka [mailto:MPokraka at samsungsemi.co.uk]
Sent: 27 November 2000 19:15
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow occasionally doesn't exec next step + Error m
essagi ng

Hi Alan,
Thanks a lot for your comprehensive input.

to 1. - yes I've gon through the diagnostics, nothing..... techn. trace is a
little out of the question on a spurious error + productive client as it
seems to all but kill our test system (short dump/ 15min timeout when saving
a sales order????).
Interesting thing though - this seems to happen when a batch of IDOC's come
in and a whole bunch of W/Flows get started in quick succession..... Will
keep monitoring and perhaps raise an OSS.

to 2. (admin not notified problem) - It is only one particular object method
error that never sends error notifications, I get them for other w/f errors,
so authorization etc is no prob. Nevertheless, I've done some rearranging to
work around it.

Thanks again,
Cheers
Michael

-----Original Message-----
From: Rickayzen, Alan [mailto:alan.rickayzen at sap.com]
Sent: 27 November 2000 14:58
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: BASIS: Workflow occasionally doesn't exec next step + Error
m essaging

Michael,
1. Did you run the diagnosis utility (SWUD) and go through the "workflow
stalled" menu?

2. You might have to open an online service ticket on the admistrator
problem you were having. But before you do, here are some thoughts on the
matter which might also help others.

In most releases the workflow engine sends the administrator mails with the
work item as an attachment (rather than assigning the work item to the
administrator). So you might want to check that mails can be sent in your
system.

Here are two situations when the administrator will not receive a mails.
>       When the flow does not start at all.
>       When the error has been modelled in your workflow to follow a
certain path.

If neither of these is true, there might be a problem with the send-mail
authorization of wf-batch or the person executing the work item before the
batch job. One last thing. If your batch job produces a temporary error
(defined in the method), then the workflow will not go into an error state
until the retries have been exhausted. Check that your flow really does have
the status "ERROR" and is not still "In process".

Good luck,
Alan Rickayzen

-----Original Message-----
From: Michael Pokraka [mailto:MPokraka at samsungsemi.co.uk]
Sent: Monday, November 27, 2000 3:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: BASIS: Workflow occasionally doesn't exec next step

Hi folks,
We've gone live with a new workflow, but it seems to not execute the first
step every now and again for no apparent reason.

Scenario: EDI order comes in, triggers W/F via event
IDOCORDERS-INPUTFINISHED.
The first step in the w/f checks the order type and does whatever.
However, every now and again (2 out of 10), it doesn't even show the
decision step in the log - simply that the main workflow was started and
nothing else........ logs show nothing, no errors, just status started. I've
checked the container & all the info is there.

If I start the w/f manually giving it the appropriate references (order,
IDOC no's), it runs fine.

Execution is also not possible since it is a workflow template, not a task.

I'd love to hear from anyone who's seen this before......
TIA
Michael Pokraka
SAP EDI Analyst
Samsung Semiconductor Europe Ltd
Tel: +44 (0)20 8380-7050
Fax: +44 (0)20 8380-7218
This message transmitted on 100% recycled electrons.

-----------------------------------------------------------------------

The information contained in this email may be privileged, confidential
and protected from disclosure. The opinions expressed are those of the
individual and not Samsung Semiconductor Europe Ltd or Samsung
Electromechanics Ltd. Internet communications are not secure and
therefore Samsung Semiconductor Europe Ltd and Samsung
Electromechanics Ltd do not accept legal responsibility for the contents
of this message. If you think you have received this email in error please
notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
copies of the mail.

-----------------------------------------------------------------------

The information contained in this email may be privileged, confidential
and protected from disclosure. The opinions expressed are those of the
individual and not Samsung Semiconductor Europe Ltd or Samsung
Electromechanics Ltd. Internet communications are not secure and
therefore Samsung Semiconductor Europe Ltd and Samsung
Electromechanics Ltd do not accept legal responsibility for the contents
of this message. If you think you have received this email in error please
notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
copies of the mail.

-----------------------------------------------------------------------

The information contained in this email may be privileged, confidential
and protected from disclosure. The opinions expressed are those of the
individual and not Samsung Semiconductor Europe Ltd or Samsung
Electromechanics Ltd. Internet communications are not secure and
therefore Samsung Semiconductor Europe Ltd and Samsung
Electromechanics Ltd do not accept legal responsibility for the contents
of this message. If you think you have received this email in error please
notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
copies of the mail.