Bad Request when using Alteryx API V3/Workflows

Bit of an odd one this, not sure whats going on but I have a workflow that migrates workflows from our Dev to Prod server (also checks if its an upgraded version or a new workflow), worked on it for ages and finally got it working a couple of months ago. Now I have a user who's been off long term and come back and cannot get the workflow to run and migrate his workflows, its also the same for me, I cant migrate his workflows either! If I take ownership of the sample workflow we created (just a text input tool, does nothing basically) then the migration workflow runs, transfer back to the user and it fails. The workflow uses my API Key since I dont want to enable API access for End Users, I am the Admin of the servers, Ive also asked users to try and the one who got back to be ran it for a workflow he created and it worked fine, so it seems that its something to do with this user, but what? The user can has permissions setup on everything other than API access (same as other users), I also added myself to his studio to see if that made a difference, it didn't - basically, anybody got any ideas of things to check?

API

Accepted answers

All comments

abacon

@craigja Are you getting a specific error message when it doesn't run? Are you running it from server or desktop? If desktop, does the user who can't run it have the correct network access to query the Alteryx server? Ports, FWs, etc.

Bacon

SGolnik

Are you able to do any part of the migration? ex you can use the api calls to see that his workflows are migratable and can download the package from Dev, but cannot upload to prod
Are you getting a specific error message?

Things that I would check....

Did anything regarding this individual change in Active Directory? ex. when they came back did they keep the same AD account or was a new one created
Pull the user details from both Dev and Prod comparing the details of both to see if there are changes. Also check to see if there are multiple users by the same name.

craigja

The error message when calling the V3 Workflows to push the workflow to Prod is - Bad Request - not the greatest error message! Everything works till this point - these API calls work:

Get all collections from Dev

Get All workflows in collections on Dev

Get Collections from Prod

Its only when I call the API to Push the workflow to Prod that we get this error. It would be the same AD account the user has, it would just have been disabled for the duration, I can check group membership and see how that looks compared to another user.

craigja

Just had a look at AD groups, nothing jumps out at me, this user and another in the same dept have the same Alteryx AD groups. Also, the API call is made using my Admin key/secret, so I supppose the issue is that I cant use the API to move their workflows, but I can move everyone elses workflows with no issues

craigja

Its now affecting more that 1 user, so something must have changed somewhere! But where.....

craigja

Just looked at one of the other outputs of the API - the L outout and in there I see an error:

{
"message": "The request is invalid.",
"modelState": {
"credentialId": [
"Invalid credential id."
]
}
}

Now the credential used is correct, I look up the credential and its valid in Prod and I also have access to that credential, so I dont know why I get this error, but at least its a bit more of a clue than Bad Request!

Gaurav_Dhama_

Once you get the all the details, test it on postman once. If it does not work there as well then check if the parameters are affecting it, like change the parameters and identify what might not be working out.

This is how I do it when any of my Alteryx APIs break in process.

Update: How are you fetching your credential ID? is it using API> GET /v3/credentials.

nbrenner

So, this may sound odd but...I have 2 workflows up, one a GET for user API call and another for PUT to update a user. The GET was working fine. The PUT was not. I copied and pasted the keys from server the same way. Just to gut check myself I did it again into notepad first then back out from notepad to Designer and low and behold, the PUT one started working. So, double check the keys in Notepad as well. Might be a life saver.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703