Restarted workflow does not continue

[Fred Lunaspa]

Michael and Mario,
 
First of all, thanks for your quick replies!
 
The changes to the workflow were implemented before we went life! So at the
moment the change (to background task) was implemented no instances were
running. I also tested a new instance on production and it fails with the
same error (on development all goes well).
 
If I remember correctly all buffers are also refreshed when the system is
restarted. So, because the system was restarted several times after the
change was implemented, that would mean that the problem should not arise.
 
Do you have other suggestions? The only thing I can add is the fact that I
changed the task to background task without first deleting the responsible
agent entry in the step. It is removed automatically from the step. Next I
only transported the changed task, not the workflow definition in which the
step is defined. Can that have caused the problem? And if yes, what to do
next?
 
Michael, what did you exactly mean with "A further complication is the good
ol' SWU_OBUF after transport to clear SAP's 'memory' ". Is using SWU_OBUF
causing complications, or should it solve these kind of problems?
 
Regards,
 
Fred
 
 
 
>From: Michael Pokraka <workflow at quirky.me.uk>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Restarted workflow does not continue
>Date: Thu, 12 Jun 2003 14:29:22 +0100
>
>Hmmm, sounds like an incompatible change to me, in onther words one which
>will break existing instances of a workflow. Also, you cannot have an agent
>for a background task. A further complication is the good ol' SWU_OBUF
>after transport to clear SAP's 'memory' as you almost correctly described
>it :)
>
>Cheers
>Mike
>
>On Thu, Jun 12, 2003 at 02:47:07PM +0200, Fred Lunaspa wrote:
> > Hello,
> >
> > We just went life and I bumped into a problem I can't solve. We 're on
>4.6C.
> >
> > A workflow started and was processed until a step that in the past was
> > assigned to a synchroneous task without dialog (general task,
>responsible
> > agent was a role that determined the purchasing group). Recently, just
> > before going life, the task has changed to a background task (just set
>the
> > indicator to background task). On development all looked (and worked)
>OK.
> > But now on production when the workflow reaches this step the following
> > error occurs:
> >
> > - WL 465 Activity 782: Responsibility 'AC9000001' is not valid agent for
> > task TS90000022
> >
> > I checked the step definition in production and no responsible agent is
> > assigned to the step (not visible in the field though). The system
> > 'remembers' something...
> >
> > I did a refresh index for the agent assignment for the task (hoped that
> > would help) and restarted the workflow instance (using SWPR Workflow
>restart
> > after error). Now the workflow is in status 'Started' (In process), but
>does
> > not continue with the step that was in error. The technical workflow log
> > still displays the same error (but as I already menitioned, the workflow
>is
> > in status 'Started' ('In process')
> >
> > Can someone help me out?
> >
> > Regards,
> >
> > Fred Kouw
> >
> > _________________________________________________________________
> > Chatten met je online vrienden via MSN Messenger.
>http://messenger.msn.nl/
 
_________________________________________________________________
MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl