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

EndTask remains active

System

TS 6.1 SP2, Win2K

I have a situation where a parent workflow spawns one or more child workflows. The child workflows are very simple, with (at the moment): externaltask -> usertask -> EndTask. The XML for this workflow is attached.

The strange behavior I'm noticing is that after a child completes the usertask, the job transitions to EndTask, but just hangs out there. In other words, I can do a iwgetwfobj on the jobid and it'll tell me that EndTask is active. Is this characteristic of nested jobs or is this weird?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

Find more posts tagged with

Comments

Migrateduser

I think you are asking if the parent job of a nested workflow will stay active until all the children have done their work and completed.

I believe the answer to this is yes.

lissa

Adam Stoller

Just to clarify - is it the parent job's endtask or the child job's endtask that you are seeing? (my guess would be the latter)
Is there a compound conditional for the parent job to transition to the next task after the wftask? If so - then it might be that the child job endtask's sit around until the parent job transitions past the wftask.
If the parent job has transitioned past the wftask and the child jobs are still sitting there at their endtask(s) - then this is probably something that Smitty complained about a while ago (I don't remember the details, I just remember some ranting about the endtask's staying active when he felt they shouldn't be) -- you can probably find his posts if you search through the forums.

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

Migrateduser

Actually, this is not what I was wondering -- doing an iwgetwfobj on this nested job's job id returns the following:


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<workflow name="Nested Approval Workflow" active="t" owner="VANGUARD\U25G" creator="VANGUARD\U25G" activationtime="1111429232">
    <description>Nested Approval Workflow</description>
    <tasks>
        <id v="30904"/>
        <id v="30905"/>
        <id v="30909"/>
    </tasks>
    <starttasks>
        <id v="30904"/>
    </starttasks>
    <activetasks>
        <id v="30909"/>
    </activetasks>
    <locks/>
    <events>
        <event date="1111429232" name="TaskAddFile" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername="">
            <arg v="enterprise\Inv_Description\ShortBulleted_Inv_Descr\5001_7500\5481.html"/>
        </event>
        <event date="1111429232" name="TaskAddFile" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername="">
            <arg v="enterprise\Inv_Description\ShortBulleted_Inv_Descr\5001_7500\5485.html"/>
        </event>
        <event date="1111429232" name="TaskAddFile" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername="">
            <arg v="enterprise\Inv_Description\ShortBulleted_Inv_Descr\5001_7500\5487.html"/>
        </event>
        <event date="1111429232" name="TaskGoActive" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername=""/>
        <event date="1111429232" name="TaskInvokeExternal" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername=""/>
        <event date="1111429236" name="TaskCalledBack" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername="">
            <arg v="0"/>
            <arg v="Success"/>
            <arg v="4"/>
        </event>
        <event date="1111429236" name="ChooseTransition" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername="">
            <arg v="0"/>
            <arg v="Success"/>
            <arg v="4"/>
        </event>
        <event date="1111429236" name="TaskActivate" user="SYSTEM" role="1" task="30905" taskname="Approve1" other="30904" othername="InitialTask"/>
        <event date="1111429236" name="TaskInactivate" user="SYSTEM" role="1" task="30904" taskname="InitialTask" other="-1" othername=""/>
        <event date="1111429236" name="TaskGoActive" user="SYSTEM" role="1" task="30905" taskname="Approve1" other="-1" othername=""/>
        <event date="1111429392" name="ChooseTransition" user="VANGUARD\U25G" role="4" task="30905" taskname="Approve1" other="-1" othername="">
            <arg v="0"/>
            <arg v="Approve"/>
            <arg v="156"/>
        </event>
        <event date="1111429392" name="TaskActivate" user="VANGUARD\U25G" role="4" task="30909" taskname="End" other="30905" othername="Approve1"/>
        <event date="1111429392" name="TaskInactivate" user="VANGUARD\U25G" role="4" task="30905" taskname="Approve1" other="-1" othername=""/>
        <event date="1111429392" name="TaskGoActive" user="VANGUARD\U25G" role="4" task="30909" taskname="End" other="-1" othername=""/>
        <event date="1111429392" name="TaskInactivate" user="VANGUARD\U25G" role="4" task="30909" taskname="End" other="-1" othername=""/>
    </events>
    <immediatetasks/>
    <variables>
        <variable key="num_approvers" value="1"/>
    </variables>
    <parenttask>
        <id v="30892"/>
    </parenttask>
</workflow>

And doing the same command on task 30909 gets me the following:


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<endtask name="End" owningworkflow="30903" lock="f" transferonly="f" readonly="f" state="inactivated" active="f" owner="&lt;no user&gt;" unactivatible="t" tryingtolock="f">
    <description>none</description>
    <activation/>
    <inactivate>
        <pred v="30905"/>
    </inactivate>
    <resets/>
    <predecessors>
        <predecessor hasactivated="t" id="30905"/>
    </predecessors>
    <comments>
        <comment date="1111429236" user="SYSTEM" task="30904">Transitioned Successfully</comment>
        <comment date="1111429392" user="VANGUARD\U25G" task="30905"/>
    </comments>
    <activationtime v="1111429392"/>
    <unactivationtime v="1111429392"/>
    <variables/>
</endtask>

Has anyone else seen this?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

nipper

That is an undocumented feature of nested jobs.

For admins who do view all jobs, it is a pain, nothing you can do about them

Much discussed a year or so ago. James, Smitty, myself (and others) in a nice long thread

Andy

Migrateduser

Your guess as to whose endtask it was is correct.

Currently, there is no explicit transition statement in the parent workflow after the wftask, other than the vanilla <successorset> values. To my knowledge, this should be sufficient for the parent workflow to proceed, but isn't this odd behavior more attributed to the child workflow?

I tried looking for previous posts before I made mine and didn't find Smitty's. If you remember any of the rant snippets, I can try to search on that

.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

Migrateduser

I tried searching the posts before I made mine. I'd like to look at that one, but can you suggest what I could search on that would (1) identify it but (2) not give me 1200 results to go through?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

nipper

How about this one:

thread

(I searched nested jobs, no time restrictions)

nipper

And another: thread

Migrateduser

<post><greeting>Andy,</greeting>

<intro>Thanks for that -- well, </intro><sarcasm>it's nice to see that it's 15 months later and I'm working in 1 release and 2 service packs later and the item still hasn't been fixed.</sarcasm><conclusion>So, I guess I should just write this off as an IW bug and maybe be creative and figure a way around it?</conclusion>

<closing>
Thanks,

Dave
</closing>
</post>

P.S. I'm on a bit of a sugar high, so that explains the needless XML. Also, please don't ask me for my DTD.

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

nipper

Need to remember this was a high priority for Smitty. That gave it the kiss of death.