GraphQL Mutation "Success" Even When Returning Error — How to Properly Handle in Workflow?

[amrselim]

I’m using a GraphQL backend for my authentication system (register/login), and I’m running into a strange issue in WeWeb:

When the backend returns an error (like duplicate email), it still shows as “Succeeded ” in the workflow, since GraphQL returns a 200 OK even when there’s an error in the errors array.

I tried adding a Run JavaScript step after the API call to manually check for context.response.errors[0] and throw a new error to trigger the onError path. It seems to partially work, but I’m not sure if this is the best or most reliable way.

[Agustin_Carozo]

Hi Omar, welcome to the community

Have you tried reaching out to our support?

Gather all the information you can about your case and submit it.
But head’s up, if this is an issue related to GraphQL we won’t be able to help you