Getting error "A dynamic action error occurred." with the Jira Spoke

stacybentley
Tera Guru

Hi,

When using the Jira Spoke in Flow Designer to Create an Issue we are getting the error "A dynamic action error occurred.".  If we ignore the error and use pills to set all of the values it works and all of the data is sent to Jira and an Issue is created.

We want to be able to populate field that are not designated in the Spoke and should be able to click on the +Add Field Value button but it is greyed out.

I have triple check the values in the Connection and Credential records and it all appears fine.

Does anybody know what could be causing this error?

Thank you, Stacy

1 ACCEPTED SOLUTION

ServiceNow Tec2
Mega Sage
This has been resolved by ServiceNow Technical Support. Please refer to KB0818189 for more information.

View solution in original post

5 REPLIES 5

Ed41
Mega Guru

I am also running into this, but only with one of our 2 jira environments.  It "was" working perfectly fine a few days ago when I was working on development but today I get the error when attempting to update the Jira action.

Community Alums
Not applicable

I was able to fix this in my instance... The custom fields request tied to "Create Issue" had timed out. Here's what I did to resolve:

  1. In flow designer, open the most recently run operation of "Get Creatable Fields". Note the error - something like "Request not sent to uri= <your Jira instance URL> : java.net.SocketTimeoutException: connect timed out"
  2. Copy the three input runtime values used in the failed action - Connection Alias, Issue Type, and Project Key.
  3. Open the "Get Creatable Fields" flow action, and click "Test Action".
  4. Paste the values you copied in step 2 & click "Run Test".
  5. If/when it completes successfully, close and re-open the flow that was giving the dynamic action error message, and it should load properly.

ServiceNow Tec2
Mega Sage
This has been resolved by ServiceNow Technical Support. Please refer to KB0846282 for more information.

ServiceNow Tec2
Mega Sage
This has been resolved by ServiceNow Technical Support. Please refer to KB0818189 for more information.