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; } } }

How to manually invoke URL Task

fiquebem

I'm using TS 7.0 on Windows 2003. I have a WorkflowModeler Deploy Task (actually a URL External Task) in limbo after an OpenDeploy Receiver hung up. I've restarted the Receiver but the Deploy Task is still Active. How can I transition this task to the "failure" successor-set? (Unfortunately, there's no "timeout" transition on this task at the moment.)

I tried pasting the following into a Web browser window: myhostname/iw-cc/urlexternaltask?successTransition=Deploy+Success&failureTransition=Deploy+Failure&taskID=732856&jobID=732837.

But that resulted in an error page and the following message in content_center.log: ERROR com.interwoven.ui.teamsite.workflow.task.URLExternalTaskCommand () - external task: --is invalid

Using "task_id" and "job_id" as the parameter names (instead of taskID and jobID) didn't help either.

The "iwtaskselect" command-line tool can be used only with User tasks.

Suggestions?

Thanks,

S.

Find more posts tagged with

Comments

Adam Stoller

Have you tried using the iwcallback CLT?
I cannot say I've ever tried running it on a task with both a success and failure transition, but you might be able to do so.

You could also try restarting the OD service on the sender - which should cause the deployment to "fail" and thus trigger the failure transition.

fiquebem

Have you tried using the iwcallback CLT?
I cannot say I've ever tried running it on a task with both a success and failure transition, but you might be able to do so.

Thanks, iwcallback worked beautifully. I had forgotten about it. I had searched for commands with "task" in their name, so only found "iwtaskselect." Perhaps this CLT should have been named "iwtaskcallback"

Ouch! All that Workflow Modeler and Java stuff is taking its toll on me.

You could also try restarting the OD service on the sender - which should cause the deployment to "fail" and thus trigger the failure transition.

That's a thought, but with no active deployments (according to iwodserverstatus), I don't think that would help.

Thanks again,

S.