CGI task not starting in WFM on CCStd

Hi,
I have my workflow in WFM. The first task is a cgi task for which I wrote a custom cgi script and the second is the metatagger task. The workflow is executing ok the first time. If, for example, I cancelled out of the Metatagger screen, a cgi task will be pending in my task list (this is expected). However, if I execute the same workflow on the same file (let's call it my_dcr), a new job is created, but no tasks at all. The created job is pending on my task list as well.

This is happening only if the selected file is in a job created by WFM. That is, if the file my_dcr is associated to a task created by WFM, the second time I try to run the WFM workflow, a job is created with no tasks in it.

Even more, this is happening only in CCPro not in CCStd.

Has anyone run into this issue on WMF? Please let me know as this is a pressing issue for us.

Find more posts tagged with

Comments

Pawan

Hi,
I have my workflow in WFM. The first task is a cgi task for which I wrote a custom cgi script and the second is the metatagger task. The workflow is executing ok the first time. If, for example, I cancelled out of the Metatagger screen, a cgi task will be pending in my task list (this is expected).

When you cancel the metatagger task, the active task in your task list should be metataggertask and not cgitask.

However, if I execute the same workflow on the same file (let's call it my_dcr), a new job is created, but no tasks at all. The created job is pending on my task list as well.

What is the state of this second job, I mean the state of the first task of this job.
What is the cgitask doing?

Even more, this is happening only in CCPro not in CCStd.

This statement and the title of your thread are in conflict. Please confirm. Please specify your TS and WFM version.

Annad

When you cancel the metatagger task, the active task in your task list should be metataggertask and not cgitask.

What is the state of this second job, I mean the state of the first task of this job.
What is the cgitask doing?

This statement and the title of your thread are in conflict. Please confirm. Please specify your TS and WFM version.

When I cancelled the metatagger task, the active task is a Metadata task(not CGI task, my mistake).

The first cgi task is there to parse the selected folders to get the DCRs in them and attach those files to the workflow.

This is happening only in CCPro (I changed my title on this thread. Thanks)

Anna

Annad

Hi,
I just confirmed that it also does not work on CCStd.

Thanks,
Anna

Pawan

Your first task is the cgi task, so the cgi task is doing some validation before attaching the files with the job. You should debug your cgi script. I haven't heard of any issue with one file attached to multiple WFM jobs/tasks

ISCBorisB

Hi,
I just confirmed that it also does not work on CCStd.

Thanks,
Anna

Are you locking attached Files? If you are, for the second WF an Engine will try to obtain locks again and again (after
some timeout), possibly indefinitely.

HierarchyData.zip

Annad

Hi,
I think that solved the problem. It was the lock.

I set the lock option to be false and that was it.

Thanks,
Anna

ISCBorisB

Hi,
I think that solved the problem. It was the lock.

I set the lock option to be false and that was it.

Thanks,
Anna

If you do need locking you may consider using dedicated <locktask> instead of some other Task 'lock' attribute.
This way you can detect locking success/failure and fork your Flow accordingly.