After further investigation, we have confirmed when using an API Request action, API errors may still result in a task completing successfully. This is expected behavior. To view API errors, download the full response data.
More details on this behavior can be found in our Help Center: https://help.zapier.com/hc/en-us/articles/12899607716493-Set-up-an-API-Request-action#h_01H95JPYYV3DZFJCSXERAMNXNX
We apologize for the confusion and for mistakenly treating this as an incident. If you have any further questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help.
No components marked as affected
Resolved
After further investigation, we have confirmed when using an API Request action, API errors may still result in a task completing successfully. This is expected behavior. To view API errors, download the full response data.
More details on this behavior can be found in our Help Center: https://help.zapier.com/hc/en-us/articles/12899607716493-Set-up-an-API-Request-action#h_01H95JPYYV3DZFJCSXERAMNXNX
We apologize for the confusion and for mistakenly treating this as an incident. If you have any further questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help.
Investigating
We're currently experiencing an issue where steps using "API request (Beta)" Actions that are failing with a 400 error are incorrectly showing a "success" status in the Zap Run history. We are actively investigating this issue.This incident primarily affects the visibility of the success and failure status of your API requests in the Zap Run history.Please note that there's no known workaround at the moment.We understand the importance of accurate status updates and apologize for this inconvenience. As we investigate further, we will continue to provide updates.For any concerns or additional assistance, please don’t hesitate to reach out to our support team.
