There was a problem and we couldn't run the automation "{0}"

[Marco Affuso]

GoodMornig ,

I have a automation role  that send a web request with the following parameters : 

token=glptt-0c0b9f17f3d1fcf4214ebbd30431b55a34947dba&ref=master&variables[JIRA_CARD]={{issue.key}}&variables[CASH_DESK_NAME]=sprint_c5&variables[CASH_DESK_TYPE]=ssc-eft-fiscal&variables[START_JOB_JIRA]=yes&variables[DRIVER_TYPE]=web&variables[CUSTOMER_NAME]=esselunga

When run this role , I have the following errore :  

There was a problem and we couldn't run the automation "{0}"

Could we help me ?

Thank you very much

[Bill Sheboy]

Hi @Marco Affuso -- Welcome to the Atlassian Community!

For which rule step did you see that error, or was it shown in the UX when manually running the rule from an issue?

Also, it may provide context to post an image of the audit log details showing the rule execution (with all of the details at the right side of the log entries expanded).

Kind regards,
Bill

[Bill Sheboy]

Also, does your manual trigger have User Inputs? 

It does not appear to do so in the rule image, but there is an open suggestion / defect that when user input is too long for a field that error is shown: https://jira.atlassian.com/browse/AUTO-1543

[Marco Affuso]

Good morning @Bill Sheboy ,

The step for which I get the error is the one blued.

I run the role manually ( in attach the screen)

Then in the Audit Log section, there is no file with today date.

I have not imput parameters so I don't think to be in the case of the bug that you suggested

[Bill Sheboy]

In that case, if you are on a paid Jira license (i.e., not Free) I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support here:

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

They may see something in their internal logging to explain this symptom.  When you hear back from them, please post what you learn to benefit the community.