Workflow Goes To Error Status (Dale Brown)

[stephane]

Hi Dale, 

This is standard behavior, what you did in your workflow template is a
change without changing the workflow version.
You should have changed the workflow version, then all the old workflow
(started before the change) could have continue with the old definition.
However as you have not changed the version, it believe the definition
started is still valid but 'can not find it' meaning you are in
trouble... 

For the production my advice would be to stop the workflow started
before and trigger the event that will trigger the new workflow.
When changing a workflow definition already in production you shall
change the version.

Best regards
Stephane



Le mercredi 15 mai 2013 à 12:51 -0400, sap-wug-request at mit.edu a écrit :

> Send SAP-WUG mailing list submissions to
> 	sap-wug at mit.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
> 	sap-wug-request at mit.edu
> 
> You can reach the person managing the list at
> 	sap-wug-owner at mit.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SAP-WUG digest..."
> 
> 
> Today's Topics:
> 
>    1. Workflow Goes To Error Status (Dale Brown)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 15 May 2013 14:14:11 +0000
> From: Dale Brown <dale.brown at duke.edu>
> Subject: Workflow Goes To Error Status
> To: "sap-wug at mit.edu" <sap-wug at mit.edu>
> Message-ID:
> 	<1311B5D8F69C1E4A9FD4F302EC6A0314E7206E at ex-mbg-05.win.duke.edu>
> Content-Type: text/plain; charset="us-ascii"
> 
> We have a main workflow that has several steps, and one of those steps calls a sub-workflow.
> 
> We made a change to the main workflow where we moved a branch of steps from one  place in the main onto another branch in the main.
> 
> The change was not directly after the sub-workflow step in the main, but later on in the workflow process.
> 
> The issue we are running into, is that any workflow that was already in process via waiting for user decision action in the sub-workflow,
> 
> will now go into an error status when the  user does the action , which is done via using UWL.
> 
> It seems like the remaining sub-workflow steps run fine, but the flow will not continue back into the main.
> 
> The error status message in red on the main workflow is (3 lines) :
> 
> "Status change from COMPLETED to READY is not allowed/possible."
> 
> "Error at point of synchronization (work item [it lists the next work item number that you cannot see in the log] EXECUTE)"
> 
> "Work item [it lists  the main workflow item number] : Object FLOWITEM method EXECUTE cannot be executed"
> 
> 
> 
> Any newly created workflows work fine.
> 
> 
> 
> We tried swu_obuf, etc.
> 
> Would release status on a workflow template or standard task matter at all?  Currently we have them at "not defined" instead of "released" .
> 
> Is there anything in XML code that could cause this ?
> 
> 
> 
> We are on Release 720
> 
> 
> 
> Dale Brown
> 
> Duke University
> 
> OIT Application and Database Services
> 
> (919) 684-5341
> 
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130515/80457cb1/attachment-0001.htm
> 
> ------------------------------
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> End of SAP-WUG Digest, Vol 102, Issue 10
> ****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130516/546ff980/attachment.htm