Hello - it looks like the behavior of Deactivating a Source HTTP Webhook changed.
It was returning a 400 bad request for years when deactivated, but now returns a 200 with a custom response leading to the documentation.
Was this change intentional?
Bump
Hello @DFPipedreamUser,
Could you share more information regarding how you can “Deactivating a Source HTTP Webhook changed”? I’m not sure that I understand the action you’re performing.
There is a way to “Activate/Deactivate” Sources, either manually (see screenshot below)
Or, through the REST API through the “active” flag (REST API)
I see, may I ask if the API still works as expected when the response changed?
I think @pierce will have more context to answer this quetion.
The API used to return a 400 Bad Request for years when deactivated, but now returns a 200 OK response instead.
I feel like this is misleading because 200 means success for the caller but it isn’t really.
This sounds like an internal change happened, it may have been a mistake.
Could you please start a GH issue here? https://github.com/PipedreamHQ/pipedream/issues/new/choose
From there we’ll be able to triage and bubble this up to the Engineering team for an explaination.
Thanks!
Done
1 Like