Task cannot be finished, because it is no longer active

Hi All,

I am currently getting to grips with the WFM and have been trying to incorporate a simple URLExternalTask into my workflow that at the moment simply transitions to the next task.

Now I can see in the content_center log that the "chooseTransition" method is successful however I seem to get a popup that reads

"Task Test Task (17227) cannot be finished, because it is no longer active"

Has anyone came across this problem before?

Find more posts tagged with

Comments

nipper

Only time I have seen this is when there is a code issue in the external task. The callback could be executing twice or it has the incorrect value,

What OS ? What Rev of TS ? What type of task ? Perl or Java ?

Lewismcm

Only time I have seen this is when there is a code issue in the external task. The callback could be executing twice or it has the incorrect value,

What OS ? What Rev of TS ? What type of task ? Perl or Java ?

Hi nipper,

Its on Windows, TS 7.2.1, It is the OOTB URLExternalTask (java) plugged in to my WFM.

The code literally only does

task.chooseTransition("task success", "task completed");

at this point.

I can see in the logs that this works fine and I have tried logging the name of the task returned from this method and again its correct. However it seems that some other task is trying to "transition" this task again.

Adam Stoller

Hi nipper,

Its on Windows, TS 7.2.1, It is the OOTB URLExternalTask (java) plugged in to my WFM.

The code literally only does

task.chooseTransition("task success", "task completed");

at this point.

I can see in the logs that this works fine and I have tried logging the name of the task returned from this method and again its correct. However it seems that some other task is trying to "transition" this task again.

If the code is that simple, could you post the entire code rather than just the line you think is an issue?

It's possible that the problem has something to do with the context that we cannot see [yet]

NewspaperLayoutFinal.rptdesign

nipper

I agree with Ghoti

While you may not be calling the callback twice, you could be sending it the task ID of a task that has already (maybe long ago) completed

dataelement.jpg