This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Using the Interactive Documentation page for the Server API on our in-house Alteryx Server (i.e. not on the public gallery), I can execute the POST request but the workflow in my private studio is not queued (i.e. it doesn't run). The same occurs when using our custom API client, but only for POST. GET requests work as expected.
Is there something we're missing with trying to submit a POST request? I can understand if our custom API client was the issue, but not being able to submit it from the Interactive Documentation page has me concerned. Is there something in the Server config that I could point my server admins to look at?
Ok, not quite a "user Id-10t" error, but close! :)
I guess I didn't understand that the API submission would not also show up in the log of run workflows/apps that is presented to users in the web GUI.
Turns out my issue was that the workflow submitted via the API request did have have access to the workflow credentials saved with the workflow from Designer, nor did it have access to the workflow credentials given to the private studio. Hmm.... okay, I'll let that go for now and see if my server team can figure that out. Right now I need to focus on getting the API client working.
Basically, we needed to run this python script from the command line using a Control-M agent on a Windows server. Using argparse, it was easy to set up the command line parms to pass in the information needed by the script, include flags to switch to check Job Id (this is the 'id' in your response) status instead of submitting an App Id to run. You can use the https://<your.server.address>/gallery/api-docs/ to run the API to test this out.
If you do not need to run from the command line, you could make your python solution more elegant.