Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe CogniRunner 3.3.0 sources reviewed do not document a way to pause an in-progress rule until a Jira issue reaches a chosen state and then resume it. They describe event listeners and scheduled jobs, but provide no verified wait step, resume mechanism, or timeout settings for this use case.
What CogniRunner 3.3.0 documents
The Atlassian Marketplace lists CogniRunner 3.3.0 as a Jira Cloud app by LeanZero SRL, released September 7, 2026. Its listing describes three capabilities: listeners that react to Jira events, scheduled jobs that run on cron, and a Rules REST API for provisioning those two rule types. Atlassian Marketplace listing
LeanZero’s September 9, 2026 release article says, “A listener reacts to a Jira event.” It describes listener filters for project, issue type, JQL, changed fields, and comment regular expressions; a listener may also have an optional plain-language AI condition. The article describes scheduled jobs separately as cron-based. LeanZero release article
Why there is no verified wait-for-state recipe
Neither source specifies a CogniRunner action that pauses an executing rule until an issue matches a state, nor does either explain how such a rule would resume. They also do not establish timeout behavior or a polling interval. That means the reviewed documentation is insufficient to give reliable setup steps; it does not prove that the full app has no such capability.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
A listener is described as reacting to a Jira event, while a scheduled job runs on a cron schedule. The sources do not say that either acts as a durable wait inside an already-running rule. Treating a listener or scheduled job as an equivalent substitute would therefore go beyond what the documentation establishes.
What to do before building this automation
- Check CogniRunner’s current in-app documentation or ask LeanZero support whether version 3.3.0 supports pausing and resuming a rule based on a Jira issue’s state.
- Ask for the exact configuration fields, how the rule resumes, and what happens if the issue never reaches the requested state.
- Do not assume that a listener filter, JQL condition, AI condition, or cron schedule provides those wait semantics unless the vendor confirms it for your specific setup.
Do not follow ServiceNow instructions for CogniRunner
ServiceNow documents a separate “Wait For Condition” action with a record condition and optional timeout. Those instructions apply to ServiceNow, not CogniRunner, and do not establish that CogniRunner has the same action or behavior. ServiceNow documentation
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
