nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Could not add suuccessors

pani

Hi,

I am getting a problem while initiating my workflows.This Error occurs when i click the runjob button in the job initiation form.

The Error is could not add successors for task (taskname).Error:00920 object being looked up was not found.

This problem is for all the workflows.

Teamsite:6.7.1
OS:Windows 2000 server

Can anyone help me out on this problem.

Cheers,
Pani

Find more posts tagged with

Comments

Antharix

Check the task definitions in the work flow. Each tash (except the main) task will have one or more predecessor task and one or more successor tasks defined.

Check for the same.

Note : end task will not have successor task as it will be the last task in the workflow (logically).

Phanie

Are all your workflows with .wft or are they build with workflow modeller.
There is an bug that was reported for workflows that are being built with workflow modeller and when they transition from an external task to an end job directly without any task in between. Bug was covered in sp1 release.

--
Phanie

kaalraa

Hi,

I am getting a problem while initiating my workflows.This Error occurs when i click the runjob button in the job initiation form.

The Error is could not add successors for task (taskname).Error:00920 object being looked up was not found.

This problem is for all the workflows.

Teamsite:6.7.1
OS:Windows 2000 server

Can anyone help me out on this problem.

Cheers,
Pani

Try to take debugging output of the workflow to analyse the issue between discrepancy between task declaration and its successors.

pani

Hi,

I am attaching my job specification here.

I have a start task and an end task.

I am getting the same error which i have mentioned above.

There is no workflow modeler all are Workflow Templates.

Cheers,
Pani

Antharix

In the END task add

"predecessor v=Task1" . this will resolve the issue.

You can debug the WFT by setting paramenter "debug = true or 1" in the workflow.

pani

Hi,

I have tried with all the scenarios (adding predecessor).No luck.

This is problem with all the Workflows.

Cheers,
Prabhu

Migrateduser

Hi,

I have tried with all the scenarios (adding predecessor).No luck.

This is problem with all the Workflows.

Cheers,
Prabhu

Hi,

You have not set description attribute of the endtask. Set this attribute

description="End Task">

This should resolve the problem.

Rajesh

auli

Hi,
Code will run fine if Areavpath and Filepath values are correct.
Just check whether they are correct. Can you post the code snippet added in the available_templates.cfg for this workflow.

-Auli

pani

Hi,

Attached is the code snippet added in available_templates.cfg

Cheers,
Prabhu

auli

You can debug the WFT by setting paramenter "debug = true or 1" in the workflow.

Try debugging as mentioned by Antharix.

Phanie

Hi,

I am attaching my job specification here.

I have a start task and an end task.

I am getting the same error which i have mentioned above.

There is no workflow modeler all are Workflow Templates.

Cheers,
Pani

Not sure if the attached Jobspec.txt is your entire workflow but when we get an error "Could not add successors for task ****" its an indication that there is a in the noted task which refers to a successor task by name that doesn’t exist. Good that we need to check spellings of each task this is what I do.

Just a point which could of some help.
--
Phanie

Adam Stoller

In the END task add
"predecessor v=Task1" . this will resolve the issue.

You can debug the WFT by setting paramenter "debug = true or 1" in the workflow.

First of all - there is no such tag in WFT's as "predecessor" - there is a "pred" element which is part of the "activation" container element - but you shouldn't need that unless you're dealing with a concurrent workflow process - and definitely not for a workflow as simplistic as what was posted.

Adam Stoller

Hi,

You have not set description attribute of the endtask. Set this attribute

[html]
description="End Task">
[/html]

This should resolve the problem.

Rajesh

The description attribute is IMPLIED - which means that it is optional - so setting it should not have any effect (if it does, it's a bug)

Adam Stoller

Try debugging as mentioned by Antharix.

I agree - the jobspec.txt posted in post 5 seems to be visually correct - such that I wonder if it is really the job spec of the problematic workflow.

pani

Hi,

I have stopped all my teamsite process and deleted my workflow store and tried to initiate it.

The workflow works fine.

I have no idea what should is the exact problem.

Cheers,
Prabhu

Antharix

You may close this thread now.