Automagic Forum

I have a flow, where I use the "HTTP Request" trigger to launch a flow and transmit a few characters of information to the flow.
It all works fine, except the web server listening to the requests only seems to answer once the flow has completed.
Starting another flow with the "start flows" action does not change this behavior, even if "wait for flows to finish" is not checked (the web server waits for both flows to finish before it answers).
If the flow takes longer than a few seconds to complete, or performs actions (like turn of Wifi) that prevent answering the request at the end of the flow, the client sending the request will perceive the server as not responding.

Is there a workaround or a different reason for my problem?
Would it be possible to have the web server respond immediately (possibly via option in the trigger, if there is a scenario where doing so would not be desirable)?

I never tested it out until you asked. My flow which use this HTTP trigger is short. So the response is almost instant. It seems to be designed this way or maybe it is a bug (wait for Martin's confirmation). Tested with execute flows also need to wait until the flow finish, regardless the wait option. Tried using Write HTTP response + debug dialog to pause the flow, it still will wait until the I confirm the debug dialog first, before the response is sent back (even though the write HTTP response is executed already!)

For workaround, there are a lot. But I would prefer the Send broadcast/General Broadcast method (look at my index), because it is almost instant. For the flow you need to execute, add another trigger, General broadcast, and put something, example com.automagic.http.helper. Then in the HTTP trigger flow, don't use execute flow, but use Send broadcast, put the same intent, com.automagic.http.helper. Send broadcast is considered an immediate action, so execution is very fast. I tried it already, the response will be sent back even though the other flow is still executing (I pause it using debug dialog too).

Hi,

The trigger HTTP Request waits until the flow ends so all actions Write HTTP Response Text had a chance to write the desired text to the response. An exception is action Write HTTP Response File which writes the HTTP response immediately. You could use the action Write HTTP Response File directly after the trigger to answer the HTTP Request immediately even when the rest of the flow is still running. The file can also be empty if you don't want to return any data at all.
Let me add a distinct action that can be used to finish the HTTP response. Using the action Write HTTP Response File for this purpose is not intuitive at all.

Regards,
Martin

Thanks Martin for the confirmation. So it is designed this way, but somehow not effective to some usage. Maybe add a checkbox in the Trigger HTTP Request? Something like "Sent response immediately" ? Or add the checkbox to the action Write HTTP Response?

Yes, adding the checkbox is a good idea. It's probably easier to find than a new action.

Regards,
Martin