Workflow error

[Mike Pokraka]

Hi John,
Sounds like your fork is inside a loop. The fork completes based on your
event, it loops around and tries to re-enter the fork but one of the
branches is still active.
This can happen either because a) synchronization was such that the too
slow in terminating the original task. This is IMO not how the system
should work; or b) the system couldn't terminate the original task because
it was locked. Perhaps a user has it open. This is not normally a problem,
as the flow continues and the error monitoring job completes the open task
when it becomes available again.

Cheers
Mike

John A Haworth wrote:
>
>
>
>
> Hi
>
> I am seeing an error message from within my workflow log that hopefully
> someone could help me understand. The error occurs when a modelled
> deadline
> is activated.
>
> Fork from node 840 has not been released again yet
> Diagnosis
>
>
> The fork from node 840 cannot be entered again yet in workflow no. 1702875
> since it still contains open activities which may result from a previous
> loop pass.
>
>
> System Response
>
>
> The response from work item 1702882 was terminated and ignored.
>
>
> Procedure
>
>
> A fork with m branches which is already completed after n paths (n < m)
> can
> only be entered again when it no longer contains any open activities ,
> that
> is the workflow was resumed after the relevant join node.
>
>
> Check the process using the workflow log.
>
> The task with the modelled deadline is within a '1 of 4' fork. If the
> deadline is passed, the new path issues a 'deadline' event and another
> fork
> path is listening for the event and continues, coming out of the fork,
> when
> the event is raised.
>
>
> Hope I have made explained myself.
>
>
> Many thanks
>
>
> John
>
>
>
>
>
>
>
>
>
> ----------------------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
> written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose.
> ----------------------------------------------------------------------------------------
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>