Failed to invoke PAG connector command error in AD workflow

SailPoint Human Fabric (SHF) SHF Discussion and Questions
, ,
1

I have a workflow that has previously worked with no issues that, when triggered, will write to Active Directory to modify an extension attribute on a group. This weekend, the workflow began failing with the error: Failed to invoke PAG connector command. The full error message is below.

We have verified that there is no authentication issue and the input provided to the workflow is the exact same as before the issue began – in fact, I triggered the workflow with the same exact input as a previous run that was successful, but it now fails. Has there been some kind of update to workflows or to the Active Directory action that I am not aware of? Thanks.

Full Error: Failed to update group {{$.defineVariable1.oU}}

map[workflowErrorMessage:Active Directory: Update Group Err: task failed: activity error (type: sp:pag:connector, scheduledEventID: 19, startedEventID: 20, identity: 1@sp-workflow-worker-prd-useast1-idn-prd01-use1-f5b4fcc75-ptpp2@sp-workflow-engine): Failed to invoke PAG connector command (type: HTTP Response Returned a Client Error, retryable: false): request failed (type: Bad Request, retryable: false): 400 - 400 Bad Request (type: fundamental, retryable: true) workflowStatusCode:400]

2

Hello @akkochman,

I had a similar issue (though not with PAG) where one of the workflows suddenly started failing. After spending a lot of time troubleshooting, I discovered that one of the response attributes, X-Total-Count, had been changed. It was originally returned as X-Total-Count, but was later changed to lowercase as x-total-count. Since this value was being passed to the next step, the workflow failed due to a case-sensitivity issue.

What I would recommend is checking whether there have been any changes in the JSON output that is being passed as input. If you are using any variables from this step and referencing them elsewhere in the workflow, even a small change could cause subsequent steps to fail.

I’m not sure if this is the root cause of your issue, but I wanted to share a similar problem that I encountered in case it helps with troubleshooting

3

Hi Anna,

have you checked the same via api trigger if the same request is working fine and updating the defined attribute if not please get this checked from the postman.