Workflow HTTP Action got stuck in running state no error

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi,

I have a workflow to call a HTTP Request Action which is calling a third Party REST API (e.g. BeyondTrust Password safe creation). I have tested this via Bruno REST Client and I am able to create safe successfully. But while I simulate same thing with sailpoint workflow I am getting stuck at HTTP Request Action is keep running with no error. Can anyone come across this kind of issue? Screen shot calling SignAuth simple REST API same issue workflow got stuck at HTTP Request step. Tried to delete HTTP Request , recreated but same issue.

image
image1345×622 60.6 KB

image
image1323×586 69.8 KB

1 Like
2

Hello,

We are facing the same issue. I hope that will be fixed quickly.

Regards

3

This is when you are testing the workflow correct, not when it is running automatically? Does it happen if you test against another REST API or service, or is it specific to the BeyondTrust call?

I don’t have a service set up to test this at the moment.

4

@gmilunich This is happing in both situation while I test workflow from workflow ‘Test workflow’ option plus same while automatically trigger while event generates. I have not tested with other REST API service, this is specific with BeyondTrust call.

5

The issue occurs with all HTTP requests, regardless of the target API.
It’s related to the SaaS workflow functionality.

6

Hi, facing a similar issue. It seems to only get stuck when using an HTTP Request related action. Otherwise my other workflows seem to be working just fine.

I have two consecutive HTTP calls, in a previous run, it got stuck on the second one so the first call succeeded. All future runs where I tested this it now gets stuck in the first call.

7

Problem on our side is now solved. The operation I was trying to do was Create Source. It’s also getting stuck without any error. When I simplified the workflow and made it much shorter, it stopped getting stuck and started giving me an error.

“The server understood the request but refuses to authorize it”

Searching the difference between API ID/Secret and PAT led me to the following article

Apparently not all APIs are accessible with API ID/Secret, and I was initially using that for authorization.

I’m not sure why the workflow only started returning an error after I simplified it (I wrote the entire workflow first before running it since it’s based on a previous already working workflow), it could be that the error is entirely different on your side, pruning the longer parts might start giving you an error

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.