The current logic of hunt bot will only do the maneuver (orbiting) after it successfully locks the target enemy. However, with the jamming NPC presents, the hunt bot can never successfully lock the target thus it will get stuck in this loop of "locking-fail-locking-...". For drone ship this is not a problem because the drones will kill the jamming NPC eventually. Yet the problem is our ship will sit there still during this process and for speed tank ships like Gila it is very dangerous. Please see the log snippet below

16:54:43: BeltHunter(330)

16:54:45 (1360) Current preset = (3), Func : BeltHunter
16:54:45 (1360) List of NPCs formed, detecting current respawn, Func : BeltHunter
16:54:45 (1360) StartFightTime = 1356, anomaly hunting: True, current respawn => NULL, Func : BeltHunter
16:54:45 (1360) Respawn table is not updated during hunting anomalies, Func : BeltHunter
16:54:45 (1360) NPCs: 6, Func : BeltHunter
16:54:45 (1360) Current Respawn: Resp ID = 0 +new -del: Dire Pithi Imputor, A=2; Pith Exterminator, A=2; Dire Pithum Abolisher, A=1; Pith Eliminator, A=2; Pith Usurper, A=1; Pith Massacrer, A=1;, Func : BeltHunter
16:54:45 (1360) noWeapons: True, reattackByDrones: False, Func : BeltHunter
16:54:45 (1360) Current NPC: Name: , ID: 0, Dist: 0, AmmoType:0, Speed: 0, Hull: 0, Locked: 0, Focused: 0, A: 0 (max priority), inLk:False, Tag: 0, Updated: 01/01/0001 00:00:00, scrambling npc present: Name: Dire Pithi Imputor, ID: 16990, Dist: 9124, AmmoType:0, Speed: 0, Bounty: 19125, Hull: 2, Locked: 0, Focused: 0, S, W, A: 2 (max priority), inLk:True, Tag: 0, Updated: 01/01/0001 00:00:00, resending drones, Func : BeltHunter
16:54:45 (1360) 1133, Func : BeltHunter
16:54:45 (1360) client.ManeuveringHunter_MinAttackRange: 0, npcsCloserThenMinimalDistance: 0, Func : BeltHunter
16:54:45 (1360) NPC Respawn calculations took 236ms, Func : BeltHunter
16:54:45 (1360) Dangerous NPC: found NPC Index: 0, Name: Dire Pithi Impu (scrambling), Func : BeltHunter
* local check (1361)
* local check (1371)
16:54:56 (1371) Timeout while waiting for LockedTargetBig icon. Targeting correction. Code 1, Func : LockNPC
16:54:56 (1371) AttackNPC failed due to targeting error. Targeting correction. Code 1, Func : BeltHunter
---> 16:54:56: ExitCode 1. Method consumed 434 sec. in 113 runs (average 3 secs/run), Next Line: 430+
---> Desc: Returns 1 if in fight or during targeting correction

Is this speed tank algorithm?

If maneuvering mode is "orbit attacking NPC", bot will orbit NPC to get closer in targeting range. It does not need to lock target before orbit is started, but if NPC is in targeting range it does not start to orbit at all. Speed tank should use orbit structure instead.

To make speed tank to use NPC orbiting need to keep track what NPC was orbited and when to restart orbiting as bot will stop as soon as NPC is killed

I had the same problem.
There are no structures to orbit so ship is just stationary in space

If you use speed tank you need or structure or asteroid to orbit in anomaly. If some structures/asteroid present but not shown in overview it is possible to add them. Any anomaly should have some objects besides NPC.