Hello,
sometimes it is useful to interupt the execution of a running agent job. For example of long running jobs.
At this moment you only have the possibility do delete a job - but the job continues to run in the background ... until you stop the agent service or kill the session (if you know the id)
This feature would be nice in dx4AdminClient and csbcmd.
Regards,
Thorsten
Edit says: Typo
This is not only a quality-of-life feature.
DOXiS Workflows heavily rely on agents and them to run predictably.
Agents are one of preferred ways of interaction management between DOXiS <=> Outside Services.
If my only choice of stopping a [long-running] agent is by hard-restarting the AgentService, all other pot. running agents might be affected by that approach. And with that, workflows and their interaction with non-doxis APIs that are managed by those affected agents.
This feature, is a requirement to actually use the agent infrastructure & workflows productively.