No Successor ...

[Hill, Anna]

Are you on 4.7? 
Are you using a result parameter out of your method to branch the
workflow depending on the result of the method execution?

If your method exectues OK when tested and your bindings are all
correct, try taking the step out of the workflow, activate, and then go
back in and replace it and re-do the bindings and agent assignment...
This is a 'when all else fails...' i.e. when you know you've got
everything in place correctly but the workflow still doesn't work. If
you're 100% sure everything is correct and you are still having
problems, log off and then on again. 


Good luck
Regards
Anna

Anna Hill 
Technology Consultant

SAP (UK) Ltd
Clockhouse Place, Bedfont Road, 
Feltham, Middlesex TW14 8HD


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Maorriyan
Sent: Friday, February 25, 2005 4:34 PM
To: SAP Workflow Users' Group
Subject: No Successor ...

Good day all.
I'm wondering why certain task in my workflow get an
'No successor for node..' message every time user
execute its notification.
What make me more confuse is, this happening some time
not all the time.
All my task has valid possible agent & responsible
agent.

Can somebody giving me explanation and solution on
this behaviour? Why this error happening?

Best Regards,

Maorriyan

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug