# Tctl batch terminate stuck **URL:** \ **Category:** Community Support\ **Tags:** configuration, deployment\ **Created:** [May 20, 2022, 11:11am UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750 "2022-05-20T11:11:06Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 11:11am UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/1 "2022-05-20T11:11:06Z")
![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/6/6adb8a3addc3869314c61c6e12c47b34f4a36196.jpeg) I started a batch job using tctl batch start. The job should terminate a workflow with a specific workflowId, just for testing before doing a much bigger batch. But the job just sits idle running. ---
**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\ **Post date:** [May 20, 2022, 12:34pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/2 "2022-05-20T12:34:06Z")
Is that batch job id in your second line one you got from some other command? Asking because on fist line you say No on confirm What do you get when you try to terminate this job: `tctl batch terminate --job_id=` Was your workflow terminated? `tctl wf desc -w ` ---
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 12:42pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/3 "2022-05-20T12:42:51Z")
1. The batch job was created. I just showed how I created it and pressed No to avoid another one. 2. It was not terminated I terminated it by myself later and closed the batch job. Another example: ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/2/28e1619bb13a71f71b42bf89644a29d06320dd16.png) ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/c/cd772072defe4d47a38c2a8d37320e00a483490d.png) ## tctl wf desc -w : ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/6/6322fbfaccd3541a6cb04133f62737e81c3968b7.png) ---
**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\ **Post date:** [May 20, 2022, 12:55pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/4 "2022-05-20T12:55:58Z")
Does this happen only for that particular workflow exec or for any? Can you in your web-ui go to the [temporal-system namespace](http://localhost:8088/namespaces/temporal-system) and see if there are any failed `temporal-sys-batch-workflow` workflows? Tagging @Ruslan as well 🙂 ---
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 2:05pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/5 "2022-05-20T14:05:43Z")
> [@tihomir](#): > > temporal-system namespace ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/a/afca48c6e783c0da14eae8acdc2651d4baea3dbb.png) aah look like a connection issue ---
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 2:06pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/6 "2022-05-20T14:06:40Z")
we deployed temporal in a zero trust network so its that. ---
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 2:07pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/7 "2022-05-20T14:07:13Z")
what temporal service talk to eachother in this scenario ? ---
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 2:07pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/8 "2022-05-20T14:07:49Z")
![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/c/c409bd0ce6c13878392c742e8d8bc737350322fd.png) ahh you answered me in slack, thanks alot! ---
**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\ **Post date:** [May 20, 2022, 2:10pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/9 "2022-05-20T14:10:40Z")
It seems your worker service is unable to talk to frontend. It could be network related, but also also config related. ---
**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\ **Post date:** [May 20, 2022, 2:20pm UTC](https://community.temporal.io/t/tctl-batch-terminate-stuck/4750/10 "2022-05-20T14:20:45Z")
Its network related, we only gave as little access as possible