Queue tree and Torch oddities

Hey all.

We’re implementing some queue tree config on a client device and are running into some strange behaviour. The download part of the tree works fine under all tested conditions. However, the upload part of the tree appears to only function when Torch is running within winbox. Yes I know this sounds mad, so I’ve recorded a quick screen2gif by way of proof!

When we invoke Torch on any interface the queue named studysafe_upload (and therefore total_upload) operate as expected. As soon as the Torch interface is closed the queue fails to recognise all of the traffic.

Is this a fault on our config somewhere or is there something more sinister happening here?

The config on the device is:

/ip firewall mangle
add action=mark-connection chain=forward comment="Mark connection where Internet" dst-address-list=!RFC1918 log-prefix=internet \
    new-connection-mark=internet_conn src-address=10.228.0.0/16
add action=mark-packet chain=postrouting comment="Mark packets where Internet Download" connection-mark=internet_conn new-packet-mark=\
    internet_traffic_down out-interface=!pppoe-out-bliss
add action=mark-packet chain=postrouting comment="Mark packets where Internet Upload" connection-mark=internet_conn new-packet-mark=\
    internet_traffic_up out-interface=pppoe-out-bliss
add action=mark-connection chain=forward comment="Mark connection where Studysafe" dst-address=172.16.0.0/16 log-prefix=studysafe \
    new-connection-mark=studysafe_conn src-address=10.228.0.0/16
add action=mark-packet chain=postrouting comment="Mark packets where Studysafe Download" connection-mark=studysafe_conn new-packet-mark=\
    studysafe_traffic_down out-interface=!gre-studysafe
add action=mark-packet chain=postrouting comment="Mark packets where Studysafe Upload" connection-mark=studysafe_conn log-prefix=study_up \
    new-packet-mark=studysafe_traffic_up out-interface=gre-studysafe

/queue tree
add max-limit=40M name=total_download parent=global priority=1 queue=default
add max-limit=9M name=total_upload parent=global priority=1 queue=default
add max-limit=40M name=internet_download packet-mark=internet_traffic_down parent=total_download priority=4 queue=pcq-down-10M
add max-limit=8M name=internet_upload packet-mark=internet_traffic_up parent=total_upload priority=4 queue=pcq-up-5M
add max-limit=40M name=studysafe_download packet-mark=studysafe_traffic_down parent=total_download priority=4 queue=pcq-down-10M
add max-limit=8M name=studysafe_upload packet-mark=studysafe_traffic_up parent=total_upload priority=4 queue=pcq-up-5M

/queue type
add kind=pcq name=pcq-down-10M pcq-burst-rate=15M pcq-burst-threshold=10M pcq-burst-time=30s pcq-classifier=dst-address pcq-dst-address6-mask=64 \
    pcq-rate=10M pcq-src-address6-mask=64 pcq-total-limit=4000KiB
add kind=pcq name=pcq-up-5M pcq-burst-rate=8M pcq-burst-threshold=5M pcq-burst-time=30s pcq-classifier=src-address pcq-dst-address6-mask=64 pcq-rate=5M \
    pcq-src-address6-mask=64 pcq-total-limit=4000KiB

Hello, I found this post, I think I was going crazy, with my RB-951Ui-2HnD the same thing happens, is there any solution??? Thanks in advance

With FastTrack connection Total queues are not processed, and hence bypassed.
Enabling Torch disables FastTrack, and re-enables global queues.

Do you have FastTrack enabled?