We are celebrating the 10-year anniversary of the Alteryx Community! Learn more and join in on the fun here.
Start Free Trial

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

Internal Server Error 500 - For only some API calls

Tom-work
5 - Atom

I am trying to build a suite of tools using the V3 api. However, I have run into some issues with some API calls.

 

When I try to delete a workflow using the delete endpoint: /v3/workflows/{workflowId} I am getting a 500 'Internal Server Error'.

 

However, I do not run into this issue with multiple other API calls.

 

I haven't run into this issue with any GET calls, and have been able to use the delete collection call: Delete: /v3/collections/{collectionId}

 

Any suggestions where I should start looking?

 

Thanks!

5 REPLIES 5
Bargeton
7 - Meteor

Hello,

 

I have the same error with the delete workflow on 1 of my Gallery server (I have 3 Gallery servers: DEV, Staging, Prod).

On DEV it's working well, on Staging I have this 500 response code.

 

I've also done a post on the forum today about this.

Hope we will have an answer.

 

Alex

nehakakar
6 - Meteoroid

If you are using theforceDelete=true parameter in your DELETE request, try removing it to see if the request succeeds without it.

Sometimes, forcing a delete can lead to unexpected issues.

greg17
5 - Atom

hi, did you ever resolve this? we have the same issue - most API calls are fine, but delete gives a 500 error
-> trying to delete a non-existent workflow gives a different error
-> as does trying from a user with insufficient perms
-> the workflow can be deleted as usual via the gallery UI

edit: maybe a version issue?? - server v: 2022.1.1.42619
-> looks a bit like this issue: TCPE-858 GCSE-1759 
https://help.alteryx.com/current/en/release-notes/server-release-notes/server-2023-2-release-notes.h...

IanBaldwinInogen
5 - Atom

We're having this on GET v3/schedules.

 

Other endpoints such as GET v3/users work fine. 

 

This is a problem because we also cannot see schedules in the browser. 

IanBaldwinInogen
5 - Atom

2023.2 Patch 11 solved this for us!