Dist Agents - how to cancel

HFCDev

Hi, 

  I am working on some plumbing to cancel DA jobs that I initiate. One use case I'm trying to figure out is when the task has been scheduled for some time in the future.  If I run $DistributedAgents.MapPkg.UnMap() on my queued task, it deletes its row out of WorkerQueuePending, but not WorkerQueue, where I still have an entry with a later execution date.  My questions are 1) will this task become active at the activation date? and 2) if the UnMap function won't work on jobs scheduled in the future, is there a recommended way of dequeuing the agent job? I'd rather not go in and start messing with rows in the DA WOrker tables if I don't have to.

-Hugh

David Templeton

Hugh

 

First, thank you for not going in and messing around with the worker tables.  I can promise you, they are subject to change. 

 

The function UnMap will be removed since it creates a number of potential issues.  First, if the cancelation of a job is part of a job chain then the DA system has no clue what the ‘undo’ is.  So a better method ( currently and suggestions are always welcome ), is for the solution when the task handlers map is called check for self-implemented cancelation where the business logic of the cancel is determined by the solution not the framework.

 

Going forward, the only really viable option that really could see is to have a ‘cancel’ to stop continuing any processing.  For instance, in a job chain, do not process anymore tasks and error allowing rollup of the execution tree.  BUT artifacts would not be rolled back.  For example, a update object implementation, using a job chain to create trees of execution the chain could be rolled back BUT any objects that have been touched already would remain.  In terms of data consistency, this may leave the solution in a non-deterministic state.  Therefore scaryJ

 

David