Share feedback, ideas and get community help

Updated last year

Sending a http post just after the flow reach the last step, results 404 error

Using shared api, when the flow has reached the last step and next, I send a post message, I get a 404 error.
How is the best way I can handle it?
L
B
7 comments
Sending a http post just after the flow reach the last step, results 404 error
Well it behaves correctly since there are no blocks left it returns 404. Anything wrong with this?
Thank you for your attention. I just think that should have other specifc return type to it or a message to indicate it. Because, http 404 can be others errors and not only when there are no blocks left.
You should have a clear message though, something like "No blocks left" or else
Where? in the flow? Or handling the http api post error?
The HTTP response should have this status code: 404 but also a response body that should clearly say: Session not found.
Thank you. I will see it
Add a reply
Sign up and join the conversation on Discord