Start Task error

AmsOnline

Hi,

While starting the workflow I get the following error
"Invalid Object. Predessecor and activation inconsistent (task name)"
Can some one tell me what the problem is?

Thanks
Ams

Adam Stoller

Hi, While starting the workflow I get the following error "Invalid Object. Predessecor and activation inconsistent (task name)" Can some one tell me what the problem is? Thanks Ams

The problem is as described by the error message. Somewhere within the WFT (at least when compiled into a job specification) you have a task (e.g.: myTask) which specifies one or more predecssor tasks (e.g. previousTask) but the name provided for the predecessor task is either wrong (typo or just plain wrong) or the list of predecessors is not truly representative of all the possible tasks that specify this task (myTask) as their successor (too few, too many).

So - keep in mind that task names are 'id's which are case-sensitive - and look carefully over your wft code to make sure that all references to a task name are spelled exactly the same - if you don't find the error that way - then look carefully at any

activation

clauses you have explicitly defined (generally not needed unless you're dealing with concurrent tasks) - and either remove them (no concurrent tasks in workflow) or verify them.