Submit Web Form · Flow handling

↑ ← →

Define how the Submit Web Form Action behaves after sending form data to a remote server. Control whether execution continues immediately, waits for a response, or applies a delay depending on how the submission result is used in your workflow.

These settings also determine how response codes and timeouts are handled, helping ensure reliable form submissions when working with authenticated sessions, server-side validation, or multi-step processing flows · Flow handling explained

Flow	Details
After request	After the Submit Web Form Action sends a request, choose how the workflow should proceed: Continue immediately · proceed without waiting for a response. Continue after delay of · wait for the specified time, then continue. Wait for server response · wait until the server responds and enables the additional "Waiting timeout" options. Waiting is recommended when the submission result, redirect behavior, or server-side validation outcome is required. Immediate continuation is suitable for simple or non-critical form submissions.
Enable waiting timeout	Optionally, to prevent an unintended workflow lockdown (in case the Submit Web Form Action is waiting indefinitely), set the Do not wait longer than timeout value option and choose a procedure to perform when On timeout is reached…
On timeout	Choose behavior if the Submit Web Form Action times out: Continue Task · proceed the workflow with the next Action. Continue with · choose an Action to continue with. Stop Task · end execution of the workflow. Stop with error · terminate the workflow with an error. The On Error handler for Action will not be activated, while the On Error handler for Task will be triggered.
Process response codes	Define how specific server response codes are handled during execution: as warning · treat matching response codes as warnings. as error · treat matching response codes as errors. Handle HTTP response codes (such as 400, 401, or 422) based on how critical a successful form submission is for your workflow.
Time units	Define and set a time frame in your preferred format—be it milliseconds, seconds, minutes, hours, or days.
Variable Wizard	Use dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc.

Note

• Currently, the Wait for server response option is the recommended and fully supported flow control option.

We are here to help…

If you have any questions, please do not hesitate to contact our support team.