Workflow HTTP Request got stuck in running state but no error

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

I have created two workflows, main workflow and a subprocess workflow. Subprocess workflow has a “External Trigger”. Main workflow gets triggered when a new identity is created and then it uses the HTTP Request Action to call the subprocess workflow.

In the subprocess workflow, I have generated an Access Token that I am using in the main workflow to call the subprocess workflow.

I have tested this with the Test Workflow button on the workflow as well as automation. It gets stuck on the HTTP Request Action and does not give any error. I have also tested calling another SailPoint API but it gets stuck in the HTTP Request everytime.

Screenshot 2025-11-04 at 12.00.08 AM
Screenshot 2025-11-04 at 12.00.08 AM461×554 18 KB

Subprocess workflow:

Screenshot 2025-11-04 at 12.01.52 AM
Screenshot 2025-11-04 at 12.01.52 AM1056×531 48.6 KB

Main workflow:

Screenshot 2025-11-04 at 12.02.48 AM
Screenshot 2025-11-04 at 12.02.48 AM743×431 35.6 KB

Can someone help?

2

Hi @Binit,

Welcome to the Developer Community! :tada:

It seems there might be an issue with the HTTP operation. Could you please share the API URL you’re trying to call?

Here are a few things you can check in the meantime:

  • Verify the URL is correct.
  • Ensure the API endpoint you’re calling actually exists.
  • Confirm that the HTTP method (GET, POST, etc.) is correct.
  • Double-check your configuration — look out for typos, API version mismatches (e.g., v2 vs. v3), or incorrect parameters.
  • As a test, try intentionally entering an incorrect client ID and observe if you receive an error. If not, remove and reconfigure the operation.
3

HI @Binit ,

Can I know how you are calling the second workflow (subprocess)? Did you configure external trigger clientID, clientSecret and ClientURL in your main workflow?

Check this post Chained Workflows . It may help!

4

Yes, I have generated the client id, secret and client url in the subprocess workflow’s “External Trigger”. I am calling that from the main workflow by entering this url: https://company-sb.api.identitynow.com/beta/workflows/execute/external/workflowid

5

But I do see below token URL in main workflow which is wrong. Isn’t the token URL should be https://company-sb.api.identitynow.com/oauth/token ?

1 Like
6

Hi @ThejaC ,

You are correct. I had the Token URL incorrect. I updated it and now the Http Request goes through.

1 Like