CogniRunner 3.3.0: it no longer waits for a transition

CogniRunner 3.3.0: it no longer waits for a transition Key takeaways CogniRunner 3.3.0 (Marketplace, 7 September) adds listeners and scheduled jobs. Until now every rule needed a workflow transition to fire; now a rule can react to any of 68 Jira events or run on a five-field cron in an IANA time zone. Loops are the failure mode of event automation, so the guard rails are on by default: self-generated events are ignored unless you say otherwise, and brakes cap a listener at 120 runs and an issue at 30 runs in any five-minute window. Redelivery and loops are different problems. A brake counts r