You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
Unfortunately, that's a 3-rd party service requiring auth. Let me know how can I share a token to be able to actually call the code if it helps.
Expected behavior
Getting the expected answer, eg:
Additional context
I believe the piece used to work in previous tens of runs and only recently started to behave like this. May it be a regression? It worked on March 26 and failed on March 27.
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If this issue is continuing with the latest stable version of Activepieces, please open a new issue that references this one.
Describe the bug
HTTP Post piece seems not to work as expected in some cases.
When a specific POST request is sent with this body via Active Pieces, it returns an error:
I created a code piece that seemingly does the same thing, but it works as expected:
The unexpected server response is:
the step input is shown as:
Is it expected that it has all these backslashes?
To Reproduce
Unfortunately, that's a 3-rd party service requiring auth. Let me know how can I share a token to be able to actually call the code if it helps.
Expected behavior
Getting the expected answer, eg:
Screenshots
![image](https://private-user-images.githubusercontent.com/4466100/317514033-91458f7b-974a-4616-8e2a-a5c1618407f0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1NTk2OTUsIm5iZiI6MTcyNTU1OTM5NSwicGF0aCI6Ii80NDY2MTAwLzMxNzUxNDAzMy05MTQ1OGY3Yi05NzRhLTQ2MTYtOGUyYS1hNWMxNjE4NDA3ZjAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDVUMTgwMzE1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NGEwZWIwYjdjNDNkZWMwY2Y5ZjY2OWUyNWVhYjE1MTQ0NmNmNDQzNjkxZmE5ZGFjYTUxNmZhY2IyMDI4OTMwNSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.K_gyR-LONkpqLm0sjCa-nJ9tIj1dGTIPRpPNWyxxXp0)
Additional context
I believe the piece used to work in previous tens of runs and only recently started to behave like this. May it be a regression? It worked on March 26 and failed on March 27.
The text was updated successfully, but these errors were encountered: