rovo slack agent

[Mario]

Hi Community

A bit of a interesting error message when Rovo attempting to Raise a request when prompted it used to work before

Create JSM request button pops up but right after ticket seems not be created and get this error message after:

Tool output data:
Failed to invoke action. Errors: [{message=The request type associated with this email account has validation rules applied to one of the fields. You can either create a new request type for this email account or remove validation from the field. Please provide a valid value for field 'What is your question?', statusCode=400, extensions={errorType=DOWNSTREAM_INVALID_INPUT, errorCategory=CLIENT, retryable=false, statusCode=400}}]

[Andy Rusnak · Accepted solution]

Hi Mario, 

Thanks for using Atlassian Community!  Usually this type of message indicates that the value passed along for a field on the Request Type is invalid.  That could be something like URL is malformed or exceeds the character length.  It is difficult to tell what it doesn't like just based off that visible error message.  

A few things to potentially check: 

• What type of field is the 'What is your question' on the request type?  
  • Has there been any of these changes recently to this field (since it stopped working)?  
• What is the data that is attempting to be passed into that field by the chat agent?  

If you open a Support Issue with us and give us a time when the problem was replicated within the last 30 days, we might be able to review the backend server logs to see what is invalid about the input being passed in.  That might also provide some additional clues around what is going on.  

Best,
Andy

[Dr Valeri Colon _Connect Centric_]

@Mario  adding to what @Andy Rusnak shared—this is also a known limitation with Rovo today. When request types have strict validation (required fields, formats, assets, etc.), the agent doesn’t always populate them reliably, which leads to these 400 errors.

A common workaround is to create a simplified request type for the agent with fewer required/validated fields, then use automation to enrich or route the ticket afterward.

[Mario]

Great thank you @Dr Valeri Colon _Connect Centric_ and @Andy Rusnak 

Appreciate the assistance