Automation Workflow in ROVO shows failted to get response

[Venkatesh Parthiban_G]

I am currently building an automated Sprint Minutes of Meeting (MoM) report using the Use Rovo action block in Jira Automation. The workflow is designed to use a Lookup work items block to gather sprint tickets, map out estimates, and pass a structured prompt into Rovo to output raw HTML formatting for a final email block.

However, during rule execution, the rule intermittently returns a red FAILED status specifically on the Use Rovo component block with the error message: "Failed to generate response".

I want to understand the exact technical limitations causing this. Based on my troubleshooting, I suspect it could be related to one of the following constraints:

1. Token/Context Window Limits: The prompt feeds a flat data loop ({{#lookupIssues}}...{{/lookupIssues}}) that pulls in custom fields, labels, summaries, and parent keys for a large active sprint dataset (including subtasks). Does the payload text easily exceed Rovo's background input buffer or token window threshold?

2. Template Parsing Errors: The prompt contains an inline HTML <img> tag structured as a QuickChart URL string using strict encodings (like %23, %25). Is Rovo's internal parser crashing when handling highly specific URL query syntax, or do background string characters trigger execution breaks?

3. Execution Timeouts: Does Rovo have a hard-coded internal timeout window (e.g., 30 seconds)? If the dataset is large and the arithmetic logic requested in the prompt takes too long to filter, will it dump a failure instead of completing?

My Questions for the Community:

• Has anyone else encountered this structural "Failed to generate response" error when passing multi-step data matrices or complex HTML templates to Rovo?

• How can I check more granular log parameters to find the exact "culprit" within the execution payload data tree?

• Are there best practices to lower token sizes (e.g., limiting field queries in the lookup block JQL) to bypass this?

Any insights, workarounds, or documentation pointers from fellow users or Atlassian engineers would be greatly appreciated!

How can i find the reason for the issue "Failed to generate response" or how can i resolve the error ?

[Bill Sheboy · Accepted solution]

Hi @Venkatesh Parthiban_G 

If you are on a paid license level, I recommend asking your Product Admin to submit a ticket directly to Atlassian Support to take a look.  They will have better internal logging and can answer your specific usage questions for things not described in the Rovo documentation for use with automation rules.

https://support.atlassian.com/contact#/

Kind regards,
Bill

[Dr Valeri Colon _Connect Centric_]

Hi @Venkatesh Parthiban_G. @Bill Sheboy is right that Support is the best path for the exact failure reason because the public automation audit log may not expose Rovo’s internal timeout, context, or parsing errors. As a workaround, I’d simplify the rule: reduce the Lookup work items JQL, pass fewer fields, remove complex HTML/URLs from the Rovo prompt, and generate the chart/email formatting after Rovo responds. Also test with 5–10 issues first, then scale up.