In Jira Cloud Automation, the “Payload for custom variable is too large” error means a component is being asked to process too much data. Atlassian does not publish a universal custom-variable payload ceiling or a general Jira Automation prompt-token budget, so there is no verified byte or token number to target. The practical fix is to reduce the data entering the failing component—usually by narrowing its JQL scope or splitting 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. Jira Automation provides smart values, variables, lookup actions, and other ways to pass or store data, but Atlassian’s documented oversized-variable error concerns payload volume handled by a component. It is not evidence of a model prompt or token limit.
As an Amazon Associate I earn from qualifying purchases.
Atlassian Support gives the exact error as: “Payload for custom variable is too large, try reducing the amount of data stored in your custom smart variable”. Its troubleshooting guidance applies to Jira Cloud and was updated September 26, 2025. It does not state a maximum payload size.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhy the error happens
A component can receive too much data to process, including data originating in variables or actions such as Lookup issues. The error may occur in components such as Send web request or Branches. Filtering what is ultimately sent onward does not necessarily help if the component still receives an oversized input to process.
#1 Best Overall
Atlassian’s recommended remedy is “Narrowing the scope of a JQL query that is used with say a Lookup issues action or the Scheduled trigger that uses JQL to retrieve issues”. In practice, a broad query can bring too many records into a later action even when that action only needs a subset.
Diagnose the failing rule before changing it
- Open the rule’s audit log. Identify the exact failing component and read its error. Distinguish an explicit oversized-payload/custom-variable message from a service-limit or monthly-usage issue.
- Inspect the data entering that step. Check broad JQL searches, smart values, and lists such as
lookupIssues. The Lookup work items action returns up to 100 items, according to Atlassian’s action reference; that result cap does not guarantee the resulting payload is small enough for every downstream component. - Check whether the rule needs every matching record. Identify the specific projects, issue types, request types, and records required for the action. If the output format permits it, avoid carrying fields the action does not need.
Choose a fix: narrow the query or split the work
| Approach | Use it when | Trade-off |
|---|---|---|
| Narrow one query | The rule only needs a defined subset of the matching issues, and a tighter JQL scope will still include every required record. | Keeps the work in one flow, but reduces its scope. |
| Split the query across rules | The broad query covers independent segments that divide cleanly by project, issue type, or another logical boundary. | Preserves coverage across the segments, but requires separate rules to be configured and maintained. |
Atlassian documents both reducing the JQL scope and dividing work into logical segments—such as separate projects or issue/request types—handled by separate rules. Keep each rule’s query and component input focused on its segment.
Use variables, lookups, and properties for their intended scope
- Create variable: Defines a string-valued smart value that can be used by other actions and conditions in the same rule flow. It is useful for a derived value needed later in that flow, not an unlimited storage area.
- Lookup work items: Returns up to 100 work items. Review whether the query needs that many results and whether later components need all of the returned data.
- Set entity property: Stores key-value data on a relevant Jira entity. Atlassian does not document it as a general-purpose prompt-memory store.
- Re-fetch work item data: Refreshes issue values after changes. Use it when a later step needs current issue data; it does not reduce an oversized payload by itself.
- Log action: Helps inspect smart values while testing or debugging a rule. Use audit-log output to see what a step is handling and verify the effect of changes.
Tell payload errors apart from Jira Automation limits
Jira Automation has more than one kind of limit. Monthly usage limits count successful rule runs for a product; service limits constrain work during an individual execution. Atlassian lists examples of service limits such as JQL result size, processing time, rules per hour, queued items, and concurrency. These require different remedies from an oversized custom-variable payload, so use the audit-log error to identify which limit is involved.
Free tools Windows power users keep installed
One-click scans. No signup required.
Atlassian’s current Jira Cloud usage and service-limit documentation lists eight concurrent automation executions across a site. That is a concurrency limit, not a custom-variable size or token limit. A plan upgrade may affect monthly usage allowances, but Atlassian says plan upgrades do not raise platform-wide per-execution service limits.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Do not substitute Jira field limits for an automation payload limit
Atlassian’s separate Jira Cloud field-limits guidance lists a 1 MB cap for an individual rich-text entry, such as a description or comment. It also says a 25 MB limit for previously unbounded work-item fields begins enforcement in September 2026. Those numbers apply to work-item fields; they do not establish a custom-variable payload ceiling or a prompt-token threshold. The field-limits article was updated August 18, 2026.
Quick Recap
A practical test-and-recovery sequence
- Record the failing rule component and its exact audit-log message.
- Review the query and values feeding that component, especially broad JQL and lookup results.
- Narrow the JQL to the required records. If independent project or type segments must all be covered, create a separate focused rule for each segment.
- Run the adjusted rule on representative cases, then inspect the audit log and Log action output to confirm which step still carries excessive data.
- If a later action in the same flow needs a derived value, use Create variable; if data must be stored on a Jira entity, assess whether an entity property is appropriate.
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.
