List Actions step fails 'Bad Gateway'

Kelsey Greaves

Hello!
I've been experiencing an issue with the ‘List Actions’ step for the last few weeks and I'm hoping someone here can help.
Each time the flow runs, I receive a ‘Bad Gateway’ error for the ‘List Actions’ step. But, every other flow works perfectly fine!

I've tested the various other ‘List X’ steps in the flow and they all work. ‘Get an Action’ and ‘Get a Constituent Action’ still work fine. I've imported some of your wonderful templates for action flows, but it still fails at the 'List Actions' step!

If this is a Bad Gateway for listing actions, wouldn't all the other flows fail as well? I'm using the same connectors for everything…

Is anyone else experiencing this? Any tips for a lost soul? ?

Alex Wong

@Kelsey Greaves
going to need more details on the call that failed.

full request url, header, parameter, etc

full response header, and body

if you are using RE NXT save action list, did you confirm that list id still exist and you have access

did you potentially have more than one RE NXT environment (test, production) that you may be connected to

Kelsey Greaves

@Alex Wong Thanks for responding!
I imported Hallie's overdue action audit and ran it this morning to get this information. I think I've got it all, but please let me know if I'm missing anything:
Inputs Host (I think this is request header?) - { "apiId": "subscriptions/5c340b36-e0fa-450e-b6c2-cb7e0327fc56/providers/Microsoft.Web/locations/westus/runtimes/msmanaged-na/apis/blackbaudinteraction", "connectionReferenceName": "shared_blackbaudinteraction", "operationId": "ListActions" }
Inputs Parameters - { "list_id": "a7bd9900-206a-45f9-80c0-2bbfcbf4d418" }
Outputs Header - { "Cache-Control": "no-cache", "Pragma": "no-cache", "Strict-Transport-Security": "max-age=31536000;includeSubDomains", "Content-Security-Policy": "frame-ancestors 'self' https://host.nxt.blackbaud.com", "section-io-id": "39f2d4893f8467a03406e985f4aeaba9", "x-ms-tenant-id": "ab5a62b4-a6bf-460e-8a86-dec0f8001704", "Timing-Allow-Origin": "*", "x-ms-apihub-cached-response": "false", "x-ms-apihub-obo": "false", "Date": "Wed, 04 Sep 2024 18:52:26 GMT", "Content-Length": "273", "Content-Type": "application/json", "Expires": "-1" }
Outputs Body - { "error": { "code": 502, "source": "flow-apim-msmanaged-na-eastus2-01.azure-apim.net", "clientRequestId": "5406c542-a3b2-44fc-91cb-8e5ab45a491a", "message": "BadGateway", "innerError": { "Message": "An error has occurred." } } }

I've tried multiple action lists and we only have one environment for RE NXT.

Austen Brown

@Kelsey Greaves - Click on the “…” at the top of the list action, go down and select “+ Add New Connection” and go through the steps. Then re-test your flow.

Kelsey Greaves

Hi @Austen Brown!
I did as you suggested and the flow has unfortunately failed again.

Alex Wong

@Kelsey Greaves

• try the Get a constituent action action and provide a specific action's system record id
  • if you don't know how to get the action system record id, click into one of the action in your RE NXT, and look at the URL: https://host.nxt.blackbaud.com/constituent-actions/records/197683 (197683 would be the action system record id)
• try using Blackbaud SKY Add-ins connector's Send an HTTP request action
  

Kelsey Greaves

Hi @Alex Wong! ?
The Get a Constituent Action using the system record ID works!
Could you tell me how to find the relative path for action lists? I've never used an HTTP request action before, so I'm not familiar with the process.

Alex Wong

@Kelsey Greaves
You can find the “FULL URL” path on developer.blackbaud.com:

https://developer.sky.blackbaud.com/api#api=56b76470069a0509c8f1c5b3&operation=ListActionsAllConstituents

then it is just removing the beginning part and query parameter parts:

There is a good post that teach you how to use HTTP request:

Kelsey Greaves

@Alex Wong @Austen Brown
Thank you both for your assistance with this! The issue has been resolved.
Turns out, there was an issue with the permission scope of the List Actions step in Blackbaud's API. Austen was able to contact Support with the issue and it's been fixed!

Hallie Guiseppe

@Austen Brown @Alex Wong @Kelsey Greaves
Searching discussions for a similar issue I came across this post. I've had a flow running using the List Actions from the Interactions connector and today all of the sudden it has started to fail. The error I get is: BadRequest: "raw_message": "List Id 26c171f7-001f-4e77-8a33-451257b2ae15 not available. Returned status code NotFound."

I have confirmed the list ID is correct and the list exists in RENXT. I updated the connector. I can of course use the HTTP connector as Alex mentioned above, but just wanted to make sure I'm not missing something obvious.

If this is a connector issue, I'm unsure how to report it. @Glen Hutson @Ashley Moose can you let me know how to report an issue with a connector (if I didn't miss something here.) 😎

Ashley Moose

Hi @Hallie Guiseppe - Can you test this use the 'Try it' feature for this endpoint in the Developer Portal? If it fails there, that shows this is an issue with the API, not the connector - in which case you can file a case with Support. If it works in the Developer Portal but is still failing in Power Automate, let us know and tag @Erik Leaver - he can help get that routed to the correct team.

Alex Wong

@Hallie Guiseppe @Erik Leaver I submitted a support case for an intermittence error in FE calling Get Invoice. Odd error message too, but the default action message say "Bad Request" as well, so you need to take a look at the raw output. Support case for me is 020743950

Hallie Guiseppe

https://community.blackbaud.com/discussion/comment/310574#Comment_310574

I tested running the list using the API and I get "Bad Request" so I guess it is an API issue. @Ashley Moose when you say "support" is that Blackbaud support?

Hallie Guiseppe

@Alex Wong Mine says it can't find the list. I checked that it is still there and checked the list ID number which matches what the flow is calling. Based on Ashley's comment, it looks as though there is an issue with the API in my case.

Alex Wong

any situation where your connection to RE NXT switched to another environment?

Hallie Guiseppe

Update:
I was unable to get back and do additional testing and this week the flow is running again. I'm unsure what the issue was but it seems to have been resolved.