Get Identity Action in Workflow is not Working

This has got to be something so simple that I am just going to be embarassed when I find the answer. I have a workflow that is triggered when identity attributes change. It is looking to see if someone is going from active to inactive. It then pulls the identity to get their location, and if they work out of one of a few buildings, it emails the security team so they can revoke the badge. Yes, I know, ISC should be connected to the badge system and disable the badge directly. Technical concerns as well as politics are preventing that. This workflow worked when I wrote more than a year ago, but at some point it started failing and no one mentioned it. When I dive in, it is getting an 400 error when it tries to do the Get Identity action and I have no idea why.

unable to execute HTTP request (type: Bad Request, retryable: false): Get "``https://prd14-useast1-mice.accessiq.sailpoint.com/v3/identities/8abda9b3b3324249a2097cd6f4e3f958``": request id '94051d3030e14324b9f1c985681c14a9' failed with status 400: &{%!s(*http.body=&{0xc0068f83c0 <nil> <nil> false false {{} {0 0}} false false false <nil>}) {{} {%!s(int32=0) %!s(uint32=0)}} %!s(bool=false) <nil> %!s(func(error) error=0x784d20) %!s(func() error=0x784e00)}:

The step input is:

{
“id”: “8abda9b3b3324249a2097cd6f4e3f958”,
“method”: “GET”,
“path”: “v3/identities/8abda9b3b3324249a2097cd6f4e3f958”,
“service”: “mice”
}

The variable being passed is $.trigger.identity.id

How can this fail?

CorpSecurityTerminations20260402.json (3.5 KB)

I was not able to reproduce your error in my tenant. I uploaded your workflow definition and everything processed as expected.

Does this occur with all identities or only select ones?

The identity assigned as the owner of the workflow does not exist or does not have permission to execute getIdentity().

I had a similar error previously when my client accidentally deleted my svc_account. The workflow started throwing this error.

It happens on all identities

That would make total sense, but I created it and my account is an org_admin.

However, what I did was to change the owner, save, then change the owner back to me and save. This time, it tested without error. Interesting. I think I had better go check out the other workflows I have authored.