If a CogniRunner-protected Jira transition behaves unexpectedly, first identify where it failed: a condition can hide a transition before you select it, a validator can block or allow it when you submit it, and a post-function runs only after the transition has committed. LeanZero’s CogniRunner documentation says runtime validator timeouts and infrastructure failures generally fail open, while an empty or still-unparseable AI response is a documented fail-closed exception. Check the execution record to distinguish a completed decision from a fail-open pass or queued work.
Why is a Jira transition missing?
Check the workflow condition. LeanZero describes conditions as rules Jira evaluates before offering a transition. If a condition evaluates as false, the transition is hidden and Jira does not show a failure message. Conditions do not call AI, according to the product documentation.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Jira Mastery for Scrum Masters: Your Complete Handbook for Agile Project Excellence | $24.49 | Buy on Amazon |
| 2 |
|
Jira: The Complete Guide to Agile Project Management | $9.99 | Buy on Amazon |
LeanZero also says an expression-evaluation error hides the transition, while an unknown or unrecognized condition configuration is designed to default to true and leave it visible. These are documented CogniRunner behaviors; they should not be assumed to describe every Jira installation or workflow configuration.
Why did the transition go through after a timeout?
A timeout is not necessarily a blocking verdict. A validator runs when a user attempts a transition, and an AI-configured validator can block the submission with a message. But LeanZero says runtime validator timeouts and infrastructure failures generally fail open: Jira may allow the transition without the AI check completing normally.
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 →The product page documents these outcomes:
- Usually allowed with a logged infrastructure reason: missing provider key, inactive license, disabled rule, provider or network failure, rate limit, and runtime timeout.
- Blocked: a completed response with a genuine
isValid: falseverdict, or an empty or still-unparseable AI response after recovery.
This means a pass after a timeout does not prove the AI approved the transition. Look in the execution record for the reason and any fail-open marker. LeanZero gives “AI validation timed out — transition allowed (fail-open).” as an example log message; for an agentic context-gathering timeout, it gives “Validation timed out while gathering context. Transition allowed.” These are examples documented by the publisher, not guaranteed text for every version.
How long does CogniRunner wait?
LeanZero’s product page, accessed October 4, 2026, documents the following internal budgets. These are publisher-stated implementation values, not independently measured timings or a service-level guarantee; confirm them against the applicable product release before relying on them.
| Execution path | Documented budget | What the page says about it |
|---|---|---|
| Non-agentic validator AI call | 21 seconds | Leaves about four seconds for log writing before Forge’s approximate 25-second synchronous workflow-function hard kill. |
| Agentic validator AI work | 20 seconds | Leaves about five seconds for tool execution and logging. |
| Inline post-function | 22 seconds | Inline execution budget. |
| Queued post-function | 110 seconds | Budget inside a 120-second consumer timeout. |
LeanZero says heavier post-function tasks, including research or document generation and some MCP-backed work, are sent to an asynchronous queue. A queued task can finish after the transition dialog closes. The logs may identify the run as asynchronous and report time spent waiting in Atlassian’s event queue.
Did a post-function fail, or is it still queued?
A post-function runs after the Jira transition commits. LeanZero says a post-function failure does not roll back that committed transition, so an issue can show the new status even if follow-up work later fails. Queued work may also still be running after the user-facing dialog has closed.
Recommended Free Tools
Use the execution record to distinguish a delayed queued run from a skipped run or an execution failure. The product page describes queue labels and possible delay details, but does not establish an independent guarantee for when queued work will finish.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Where can I check whether a validation was skipped or failed?
LeanZero says CogniRunner provides a global Execution Logs tab, per-rule history, a rule view in the workflow editor, and an issue-specific panel. Depending on the view and run, records can include the verdict, reason, execution time, mode, rule identity, and AI-related details. Fail-open runs are marked, and asynchronous work is labeled as queued.
For diagnosis, match the symptom to the execution stage:
- Transition absent: inspect the condition and its expression behavior.
- Transition appears but submission is blocked: inspect the validator result and displayed reason.
- Transition passes unexpectedly: check for an infrastructure reason and fail-open marker rather than assuming the AI returned an approval.
- Transition completed but follow-up work is missing: inspect post-function logs and queue status.
Condition, validator, and post-function: which one should you inspect?
| Workflow element | When it runs | What failure looks like | AI behavior |
|---|---|---|---|
| Condition | Before Jira shows the transition | Transition is hidden; no failure message | Does not call AI, according to LeanZero |
| Validator | When the user attempts the transition | Can block the transition and show a message; runtime failures generally fail open | Can call AI when configured to do so |
| Post-function | After the transition commits | Follow-up work can fail without rolling back the transition, or complete later if queued | Some heavier work is queued, according to LeanZero |
CogniRunner behavior and the timing figures above are described by LeanZero on its CogniRunner product page, accessed October 4, 2026. The page attributes the product principle “Fail-open is the law for runtime rules” to CogniRunner’s CORE_CONTRACT.md; that is a vendor statement, not an independent standards requirement.
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.
