Describe the Bug
Although this issue is described (far down) in the documentation, it's not acceptable for an HTTP action to simply omit headers, without warnings, before making a request. The headers omitted by default are also important ones that are expected to be included.
Either don't omit these headers, or inform the user in the designer somehow. We spent multiple hours debugging this before coming to the conclusion that the workflow does not behave as defined.
Plan Type
Standard
Steps to Reproduce the Bug or Issue
- Create an HTTP action with Content-Type header and method = DELETE
- Run the workflow
Workflow JSON
No response
Screenshots or Videos
No response
Additional context
No response
AB#16556949