Problem Reassigning Certification Tasks via API

Hello!

I’m having an intermittent issue using API to reassign certification tasks. I sometimes (not all the time) get an error:

{
  "detailCode": "400.1 Bad request content",
  "trackingId": "16cdb54b6c854f4885083d98fc9e4ad0",
  "messages": [
    {
      "locale": "en-US",
      "localeOrigin": "DEFAULT",
      "text": "The request was syntactically correct but its content is semantically invalid."
    },
    {
      "locale": "und",
      "localeOrigin": "REQUEST",
      "text": "The request was syntactically correct but its content is semantically invalid."
    }
  ],
  "causes": []
}

Originally, I was attempting to make this call in a PowerShell script. I have logging on the script and most of the calls work fine, but a handful fail with the above error. I’ve been able to replicate the issue in Postman using the same certification ID, task ID, and identity ID for the reassignment call, and I’m not sure what the issue is.

Here is the body I’m passing with the IDs blurred out for security:

image

Any ideas what might be causing this error? Or why it’s only happening intermittently?

1 Like

Hi Vincent

I’ve seen this error when the content of the API wasn’t correct, is there a possibility that one of the ids might be wrong when the error occurs?

1 Like

Hi Vincent,
Have you tried reassign to different user for the same certification id?
Is that works?

Thanks,
Girish

So this is strange, after doing more research into this, what I’m finding is the tasks I’m trying to reassign just don’t exist anymore. Ultimately it seems you’re correct, the issue is the task ID I’m trying to use. I’m getting that task ID initially by retrieving all of the tasks from the certification (list-identity-access-review-items | SailPoint Developer Community), then looping through the results from that call and reassigning. But somewhere in that process, after I’ve already retrieved the task ID, the task itself seems to just disappear.

1 Like

Ah, that is strange but good to know, progress at least :).
I wonder if maybe you potentially have any work reassignment tasks setup in your environment that may be reassigning those particular tasks automatically based on specified criteria or potentially another admin reassigning the task on the GUI prior to your script running?

1 Like

So it turns out the script was trying to reassign tasks that have already been reassigned, hence the failure. Mystery solved.

Thanks!

2 Likes

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