If a Jira transition is missing, passes unexpectedly, or finishes before its CogniRunner work appears, check which workflow component ran and what its execution log says. A condition can hide a transition before you select it; a validator runs when you submit it; and a post-function runs after the transition commits. CogniRunner’s publisher says runtime validator timeouts generally fail open, while an empty or persistently unparseable AI response is a fail-closed exception.
Why is a Jira transition missing?
First check the transition’s condition. LeanZero says Jira evaluates a condition to decide whether to show a transition. If the expression evaluates as false or encounters an evaluation error, the transition is hidden without an error message. Conditions do not call AI, according to the publisher.
As an Amazon Associate I earn from qualifying purchases.
The publisher also says condition configurations are designed to treat unknown or unrecognized configurations as true. In that case, the transition remains visible. These are CogniRunner-specific documented behaviors; the source does not establish that every Jira installation or configuration behaves identically.
If the transition is visible but fails after you submit it, investigate the validator instead. A validator runs when the user attempts the transition and can block it with a displayed message. An AI-configured validator can call AI.
#1 Best Overall
When does a validator allow or block a transition?
LeanZero describes runtime infrastructure faults as generally fail-open: the validator allows the transition and records why the expected check did not complete normally. A completed, genuine isValid: false result blocks the transition and can show its reason. The publisher documents empty AI output, or output that remains unparseable after recovery, as a fail-closed exception.
| Validator outcome | Documented transition behavior |
|---|---|
| Provider key missing, license inactive, or rule disabled | Passes without performing the expected AI check under the documented fail-open policy (LeanZero, CogniRunner product page). |
| Provider or network failure, including rate limits and timeouts | Generally passes and logs the infrastructure problem (LeanZero, CogniRunner product page). |
Completed genuine isValid: false result |
Blocks and can display the reason (LeanZero, CogniRunner product page). |
| Empty AI response or output still unparseable after recovery | Blocks, according to the publisher (LeanZero, CogniRunner product page). |
So a transition that passes does not by itself prove that AI approved it: the check may have been skipped or allowed through after an infrastructure problem. LeanZero summarizes its runtime-rule policy with the product statement “Fail-open is the law for runtime rules.” That is the vendor’s stated invariant, not an independent Jira standard.
How long can CogniRunner wait?
LeanZero documents the following implementation budgets for CogniRunner. These are publisher-stated values, not independently measured timings or an assurance that every run will finish within the budget. The product page was accessed October 4, 2026; it does not state a publication date, so confirm the current release context before relying on these exact values.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Execution type | Publisher-stated budget | Qualification |
|---|---|---|
| Non-agentic validator AI call | 21 seconds | LeanZero says this reserves about four seconds for log writing. |
| Agentic validator AI call | 20 seconds | LeanZero says this reserves about five seconds for tool execution and logging. |
| Inline post-function | 22 seconds | Publisher-stated internal budget. |
| Queued post-function | 110 seconds | Budget inside a 120-second consumer timeout, according to LeanZero. |
The product page says Forge hard-kills a synchronous workflow function at approximately 25 seconds. CogniRunner’s stated budgets are intended to finish before that limit. Heavier post-function work—including research or document generation and some MCP-backed tasks—is sent to an asynchronous queue, according to LeanZero.
Why did validation time out but the transition still pass?
A timeout is not necessarily a negative validation verdict. Under the behavior LeanZero describes, a runtime validator timeout generally fails open, so Jira may allow the transition even though the AI check did not complete normally. The publisher gives these example log messages:
AI validation timed out — transition allowed (fail-open).Validation timed out while gathering context. Transition allowed.
The second example concerns an agentic context-gathering timeout. Look for the recorded reason and fail-open marker to distinguish an allowed transition during a fault from a normal positive validation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Did a post-function get missed, or is it still running?
According to LeanZero, a post-function runs after the transition commits. A post-function failure does not roll back that committed transition. Some heavier work runs asynchronously, so it can finish after the transition dialog has closed; the dialog closing alone does not establish that work was skipped.
The publisher says queued runs are labeled in execution logs, which may also identify time spent waiting in Atlassian’s event queue and call out long delays. The page does not provide an independent service-level guarantee for queue completion. Use the run record to tell a delayed queued job from a skipped run or an execution failure.
Where should I look for evidence?
LeanZero describes several places to inspect CogniRunner records: the global Execution Logs tab, per-rule history, the rule view in the workflow editor, and an issue-specific panel. Depending on the record, the documented fields include verdict, reason, execution time, mode, rule identity, and AI-related details. Fail-open runs are marked, and asynchronous work is labeled as queued.
- Transition absent: inspect the rule’s condition and expression behavior; a condition can hide the transition before submission.
- Transition rejected on submission: inspect the validator result and displayed message, then find its execution record.
- Transition passed without the expected check: look for an infrastructure-failure reason and fail-open marker.
- Transition committed but follow-up work is absent: inspect the post-function record and queue status for a delayed, skipped, or failed run.
These diagnostic steps follow the behavior LeanZero documents for CogniRunner; the product page is the source for the described log locations and fields: CogniRunner: AI Workflow Automation for Jira.
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.
Recommended Free Tools
