Is there any reason why the “Flow URL” responds as 404 when I am editing the flow?
I am connecting Moxie via ActivePieces, and when Moxie receives a 404 it removes the endpoint automatically. That means that if I have to make some changes in the Activepieces flow and right at that time some of my collages using Moxie adds a timer (for example), Active Pieces will return a 404 and Moxie will remove the endpoint. Annoying!
I asked Moxie about this, and they told me “Seems like an odd decision on their part to return a 404 just because you are editing.” According to them, other platforms respond with 401 codes instead.
But that’s the issue, the unpublished flow returning 404 error code when using the “flow url”.
“Seems like an odd decision on their part to return a 404 just because you are editing.” According to them, other platforms respond with 401 codes instead.
When moxie receives a 404 error code, it removes the endpoint because it understands that the resource doesn’t exist. As he told me after testing them, it seems like other platforms return a 401 error instead of a 404 error.
Thank you @abuaboud abuaboud. Yes, that works. @ubuntuproductions I think that is why there is a test url. Its so that it doesn’t shut off during a flow test. Makes sense. Thanks again!
The correct approach is to use the test URL, as it does capture the sample data.
The reason it returns a 404 is that, according to HTTP conventions, it means “Not Found”—indicating that the resource doesn’t exist, which is the case here.
A 401 error indicates that the resource exists, but the caller is unauthorized or not sending the required credentials, which is not applicable in this case.
It’s difficult for us to change conventions based on one provider, but I would love to understand if you’re facing any issues with the “Test Endpoint” (including user experience).
Ah, so it seems like using 404 error for this is actually the right way to go. Thank you for letting me know, they have implemented a change in Moxie now and the endpoint is not removed if it receives a 404, but rather deactivated, which is better.
But another question arises in my mind: what’s the difference between using a test URL and a live URL? Why can’t there just be one URL used for testing and for the final deployment of the piece? Why do we need to switch between them?
This Interesting question, the reason behind this that there is published and draft version.
Sometime you want to edit the flow without effecting the currently running flow, so test url is only for capturing the data without triggering the flow to run.
If you have sample data, then you no longer need for test url.
Does this make any sense? and Let me know If you have any suggestions
