Chaining topics in Kapacitor

InfluxDB 1 Kapacitor
1

I seem to be failing to chain topics. Am I overlooking something? Kapacitor v1.3

What I would like, is for any alert in my example_critical_absolute to be arrive in topic sysops, via another topic testing_errors with a public action. However, collected stays as 0:

!rik@pc411 ~ $ kapacitor show example_critical
ID: example_critical
Error: 
Template: 
Type: stream
Status: enabled
Executing: true
Created: 16 Jan 18 12:46 UTC
Modified: 17 Jan 18 12:59 UTC
LastEnabled: 17 Jan 18 12:59 UTC
Databases Retention Policies: ["test"."def"]
TICKscript:
var limit = 0.2

var data = stream
    |from()
        .measurement('testing')
    |window()
        .period(5m)
        .every(1m)
    |mean('value')
        .as('mean')

data
    |influxDBOut()
        .database('test')
        .retentionPolicy('def')
        .measurement('example_critical_mean')

data
    |alert()
        .id('example_critical_absolute')
        .crit(lambda: "mean" > limit)
        .topic('testing_errors')

DOT:
digraph example_critical {
graph [throughput="1.00 points/s"];

stream0 [avg_exec_time_ns="0s" errors="0" working_cardinality="0" ];
stream0 -> from1 [processed="4478"];

from1 [avg_exec_time_ns="0s" errors="0" working_cardinality="0" ];
from1 -> window2 [processed="4478"];

window2 [avg_exec_time_ns="0s" errors="0" working_cardinality="1" ];
window2 -> mean3 [processed="82"];

mean3 [avg_exec_time_ns="0s" errors="0" working_cardinality="0" ];
mean3 -> alert5 [processed="82"];
mean3 -> influxdb_out4 [processed="82"];

alert5 [alerts_triggered="20" avg_exec_time_ns="0s" crits_triggered="18" errors="0" infos_triggered="0" oks_triggered="2" warns_triggered="0" working_cardinality="1" ];

influxdb_out4 [avg_exec_time_ns="0s" errors="0" points_written="82" working_cardinality="0" write_errors="0" ];
}


!rik@pc411 ~ $ kapacitor show-topic testing_errors 
ID: testing_errors
Level: CRITICAL
Collected: 42
Handlers: [testing_errors_chain]
Events:
Event                     Level    Message                               Date                   
example_critical_absolute CRITICAL example_critical_absolute is CRITICAL 17 Jan 18 15:26 CET


!rik@pc411 ~ $ kapacitor list topic-handlers 
Topic          ID                        Kind       
testing_errors testing_errors_chain      publish    


!rik@pc411 ~ $ kapacitor show-topic-handler testing_errors testing_errors_chain 
ID: testing_errors_chain
Topic: testing_errors
Kind: publish
Match: 
Options: {"topics":["noc","be","sysop"]}


!rik@pc411 ~ $ kapacitor show-topic sysops 
ID: sysops
Level: OK
Collected: 0
Handlers: []
Events:
Event Level    Message Date