Recent Runs and Outcome Reference
What Recent runs is
The configuration screen displays a bounded diagnostic tail of up to 10 recent executions for the rule's field triple.
It is designed to answer: "Did this rule run, and what happened?"
It is not a complete audit log. The oldest entry is removed when an eleventh entry is written, and concurrent executions can theoretically overwrite one diagnostic entry because the current store uses a read-modify-write update.
Data shown
A run can include:
- timestamp;
- issue key;
- transition ID and name;
- operation;
- outcome code and severity;
- summary and technical detail;
- retry count; and
- duration.
Numeric source values and the calculated result are not explicit run-history fields. See the privacy guide for the current error-detail release gate.
History sharing
The history key is based only on Source Field 1, Source Field 2, and Target Field. The same field triple used on different transitions shares one bucket. Transition names in each entry identify where a run occurred.
Outcome reference
| UI label | Outcome code | Meaning | Administrator action |
|---|---|---|---|
| Updated | SUCCESS | Target field was updated | None |
| Skipped | SKIPPED_SOURCE_EMPTY | At least one source was empty | Populate both sources or accept the skip |
| Config missing | CONFIG_MISSING | Jira delivered no rule configuration | Reopen and save the post function |
| Config invalid | CONFIG_UNPARSEABLE | Saved configuration could not be parsed | Recreate or resave the rule |
| Config incomplete | CONFIG_INCOMPLETE | A required field or issue reference is missing | Complete the configuration |
| Target = source | CONFIG_SELF_REFERENCE | Target is also a source | Select a different target |
| Not a number | SOURCE_NOT_NUMERIC | A source value is not numeric | Correct the field data/type |
| Unknown operator | OPERATOR_UNKNOWN | Saved operator is unsupported | Edit and select a supported operator |
| Divide by zero | DIVIDE_BY_ZERO | Source Field 2 is zero for division | Change input or rule |
| Invalid result | RESULT_NOT_FINITE | Calculation produced a non-finite number | Review values and operation |
| Read failed | ISSUE_FETCH_FAILED | Jira issue read failed | Check availability and retry |
| Field unavailable | FIELD_NOT_AVAILABLE | Target does not resolve for the issue/context | Check field existence and context |
| Update rejected | FIELD_UPDATE_REJECTED | Jira rejected the target update | Review target type, field context, and detail |
| Permission denied | PERMISSION_DENIED | App could not read or update as required | Review app/site permissions |
| Rate limited | RATE_LIMITED | Jira throttled requests after retries | Wait and transition/test again |
| Failed | UNEXPECTED_ERROR | Unexpected execution error | Capture time, issue key, transition, and contact support |
Free-app license note
The source currently contains a historical LICENSE_INACTIVE outcome and "No license" UI label. The production manifest disables licensing. A customer-facing Free release should not show subscription-renewal messaging. If it appears, capture a screenshot and contact support because the install may be running an inconsistent build.