Automation - Payload for custom variable is too large

[Cristina Carrillo]

 I am running into this issue when attempting to send one email to each assignee containing all their issues not updated in the past 4 days. I originally was running the single email for each issue but it quickly filled my inbox. Is there another way to send one email to each assignee for all issues not updated past 4 days?

[Alex Koxaras -Relational- · Accepted solution]

Hi @Cristina Carrillo 

Why do you need the 2nd lookup inside the branch?

[Cristina Carrillo]

Took the automation from this recommendation, although the link one is for tickets due Automation rule to send single email for all issues per assignee due next week 

[Alex Koxaras -Relational-]

But yours is different that the one in the example. You didn't include the {{distinctAssignee}} on your second lookup, thus you are not narrowing down your results and your payload is big (most likely this could be the cause).

[Cristina Carrillo]

Guess I missed that, only issue now is I am unable to validate the query like before and cannot run the rule to ensure it is working as intended

[Alex Koxaras -Relational-]

You can't validate a JQL when there are smart values present. Just go for it!

[Cristina Carrillo]

Same issue

[krunoslav.majer]

Heyhey,

Any luck with this issue? I am facing the same and I am just processing roughly 40 issues with 4 fields. It worked and then it just stopped working and this issue appeared.

[Olive, Lamarr]

I am facing the same Payload issue.  Do we have a viable solution?

[Shane Sterling]

Same problem

[Eric Coidan]

Same Problem here as well. Only 47 issues and getting the "Payload for custom variable is too large, try reducing the amount of data stored in your custom smart variable"