Log in
Log into community
Share feedback, ideas and get community help
View all posts
Related posts
Did this answer your question?
๐
๐
๐
Powered by
Hall
Inactive
Updated last year
0
Follow
Sending a http post just after the flow reach the last step, results 404 error
Sending a http post just after the flow reach the last step, results 404 error
Inactive
0
Follow
L
LuizAlves
last year
ยท
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
Share
Open in Discord
L
LuizAlves
last year
Sending a http post just after the flow reach the last step, results 404 error
B
Baptiste
last year
Well it behaves correctly since there are no blocks left it returns 404. Anything wrong with this?
L
LuizAlves
last year
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.
B
Baptiste
last year
You should have a clear message though, something like "No blocks left" or else
L
LuizAlves
last year
Where? in the flow? Or handling the http api post error?
B
Baptiste
last year
The HTTP response should have this status code: 404 but also a response body that should clearly say:
Session not found.
L
LuizAlves
last year
Thank you. I will see it
Add a reply
Sign up and join the conversation on Discord
Join on Discord