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

Execute Previous task, no retry option

saumil

Hi,

The requirement is kind of, We have a External task on failure of that it's making transition to user task.
Now, I want to execute previous external task, but there is no retry option on user task.

Is there any way to do it or running out of luck.

TS 5.5.2 Solaris - 8.0

Saumil
BTWholesale | CMS
TS 5.5.2 - Solaris 8.0

Edited by saumil on 03/17/05 02:49 AM (server time).

Find more posts tagged with

Comments

Jeremy

What about adding another option in the User task that just returns to run that external task again?
Or am I missing something?

saumil

Hi,
Thanks for your immediate reply.

The thing is, hundreds of job got stuck on failure of external task.

We have already changed the workflow for resolving the issue.

Is there any way to make transition of stuck jobs ?

Saumil
BTWholesale | CMS
TS 5.5.2 - Solaris 8.0

Adam Stoller

Build an error handler into your workflow.
E.g.: All externaltasks, cgitasks would use callback 0 to transition to a usertask or grouptask for investigating the error and then transitioning back to the task which failed. The error handling task (usertask or grouptask) would need to define all possible transitions back into the normal process stream. The externaltask and cgitask scripts would need to make sure that all places where the script can fail - record [somewhere] the error situation with as much detail as possible and perform a callback of 0 before exiting. The person who investigates the error must be able to know which task triggered it so that they can select the proper transition back into the normal process stream.

This is the kind of thing you should do during initial design development of a workflow - it's much easier that way than to try to retrofit an existing workflow; though that can be done too.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

saumil

Hi,
I know that its serious mistake.
We have incorporated the things in our new approach.
But I am really interested to know,
<b>Is there any way to make transition to previous task of stuck jobs? </b>

Saumil
BTWholesale | CMS
TS 5.5.2 - Solaris 8.0

Adam Stoller

If the job is "stuck" all you can do is use the CLTs iwcallback or iwtaskselect from the command line to "force" a transition of the current "hung" task to [one of] its successor.

If you haven't built in the ability to then transition it back from that successor to its predecessor then there's no way [that I know of] to force it to do that.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

saumil

Hi,
There is no proper successor task, which can make valid transition.
am I running out of luck ?

Saumil
BTWholesale | CMS
TS 5.5.2 - Solaris 8.0

Adam Stoller

Are you running out of luck? I believe the answer is "yes".
You need to build this kind of functionality into the design of your workflow from the beginning or retrofit the design with it later - but you cannot do what you want with an existing instance of a workflow that doesn't have this functionality built into it. Once it's there ....

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com