Anyone using the new 610/620 terminating events?

[Michael Pokraka]

Hi all,
Hope this doesn't get completely drowned in all the list traffic...
Is anyone out there actually using the new version (4.7/620/610)
header-level events for terminatig/restarting workflows etc?
 
We're trying to make use of this nifty new feature but all is not as it
should be: For starters, cancelling a workflow doesn't delete the instanc=
e
linkage. This has the following interesting result when using the 'Cancel
and restart workflow' function:
 
Flow 1 receives a CHANGED event.
It gets cancelled and Flow 2 is started.
2 instance linkages still remain active.
Another CHANGED event 'cancels' both flows and starts 2 more.
Another one 'cancels' these 4 flows and starts another 4. (by now we have
4 CANCELLED and 4 STARTED flows).
...and so on, resulting in 8, 16, 32, 64... workflows. Management
sometimes like approving things - gives them a sense of power, but
methinks this might be overdoing things a bit.
 
Cancelling the flow manually has the same result - the linkage remains.
Haven't found anything on OSS, but thought I'd post here before raising a
note.
 
Anyone seen this? There are a few other oddities by the looks of things,
but at this stage I still need to investigate some more...
 
Cheers & hope you had a happy Christmas/Holiday/Mr.Hankey celebration and
have an excellent New Year.
Mike