Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →If Jira Automation reports “Payload for custom variable is too large,” reduce the data the failing component must process. Atlassian documents this as a component payload-size problem—not as a universal Jira rule-memory ceiling or an LLM token limit. The documented remedies are to narrow the JQL scope or split independent work into separate rules.
What “rule memory” means in Jira Automation
“Rule memory” is a useful shorthand for the values and data a rule carries from one action to another. In Jira Cloud Automation, the specific failure addressed here is an oversized payload passed to a component. Atlassian Support’s error text is: “Payload for custom variable is too large, try reducing the amount of data stored in your custom smart variable”.
The error can arise in components such as Send web request or branches that process data from variables or earlier actions, including Lookup work items. Filtering what gets sent later does not necessarily make the component’s input small enough: the overall data passed to that component may already exceed its limit. Atlassian’s Jira Cloud troubleshooting article, updated September 26, 2025, does not publish a numeric maximum for this payload.
Why this is not automatically a prompt or token-limit error
Jira Automation smart values and rule actions are not, by themselves, evidence of an LLM prompt. The reviewed Atlassian documentation attributes this particular error to component data-volume limits; it does not specify a model-token budget or establish a general prompt limit for Jira Automation. If a separate AI feature is involved, check that feature’s own documentation for its version-specific limits rather than applying an assumed token threshold to an automation payload.
#1 Best Overall
Do not infer an automation limit from Jira field limits. Atlassian’s Jira Cloud field-limits documentation lists a 1 MB cap for an individual rich-text entry, such as a description or comment. It also says a 25 MB limit applies to previously unbounded work-item fields beginning in September 2026. Those are field limits, not published limits for an automation component’s custom variable.
How to troubleshoot an oversized payload
- Read the audit log. Identify the failing component and the exact error. Confirm whether it explicitly says the custom-variable payload is too large or instead identifies a different service-limit or usage issue.
- Inspect the data feeding that component. Check broad JQL searches and values such as
lookupIssues. Atlassian’s Lookup work items action returns up to 100 items; that is a result cap, not a guarantee that every downstream component can process the resulting data. - Reduce the query’s scope. Limit the JQL to the projects, issue types, request types, or records the action actually needs. Atlassian’s documented recommendation is to narrow the scope of a JQL query used with Lookup issues or a scheduled trigger.
- Split independent segments when necessary. If the original query covers separable projects or types, create focused rules for those segments instead of sending the broad result through one component.
- Test and locate the remaining pressure point. Run the revised rule on representative cases and inspect audit-log output. Atlassian documents the Log action as a way to test smart values and debug a rule flow. Where the output format permits it, removing unnecessary data is a practical way to reduce volume.
- Choose storage according to the need. Use Create variable for a string-valued smart value needed later in the same flow. If data must persist on a Jira entity, consider whether an entity property fits; it is not documented as an unlimited prompt-memory store.
Choose between narrowing a query and splitting the rule
| Approach | Best fit | Trade-off |
|---|---|---|
| Narrow one query | The rule needs only a subset of the records returned by its current JQL. | Keeps a single flow, but reduces its scope; check that required records are not excluded. |
| Split into separate rules | The broad query represents independent segments that divide cleanly by project, issue type, or another logical category. | Preserves coverage across segments while distributing the work, but requires maintaining multiple focused rules. |
These are Atlassian’s documented approaches. Choose based on whether one query can be safely narrowed or whether the work divides into independent segments.
Keep payload errors separate from Jira usage and service limits
A large payload, a monthly usage cap, and a per-execution service limit are different problems. Monthly usage limits count successful rule runs for the product. Service limits constrain work within individual executions and can involve JQL result size, processing time, rules per hour, queued work, or concurrency. Use the audit log and the wording of the failure to identify which category applies before changing the rule or plan.
Atlassian’s service-limit guidance says plan upgrades may change monthly usage allowances but do not raise platform-wide per-execution service limits. Its current Jira Cloud documentation also states an eight-execution concurrency limit per site; check Atlassian’s live guidance for applicability and rollout changes. An upgrade should not be treated as a fix for a component payload-size error.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsUse Jira’s data features for their actual scope
- Create variable: Defines a string-valued smart value for use in other actions and conditions in the same rule flow. It is not a general persistent store.
- Lookup work items: Retrieves up to 100 work items. The cap bounds the number of results, but the resulting data can still be too much for a later component.
- Set entity property: Stores key-value data on relevant Jira entities. Atlassian does not describe it as a general-purpose prompt-memory store.
- Re-fetch work item data: Refreshes issue values after changes. Use it when later actions need refreshed values, not as a way to reduce payload size.
These actions solve different data-handling needs; none should be assumed to provide unlimited memory for a rule or an AI prompt.
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.
