Actions57
- 1. Manager Actions
- 2. Mouse Actions
- 3. Keyboard Actions
- 4. Browser Control Actions
- 5. Element Actions
- 6. Image Actions
- 7. Others Actions
- 8. Email Actions
- 9. Developer Actions
- 10. General Debug Actions
1. Manager → Quit/Quit_All
AI-generatedSummary
Publishes an MQTT request to quit browser sessions on the selected client. By default it closes the session for the specified Remote Port; enable Quit All to close every session on that client. It can also close external browser pages, include selected incoming fields, wait for a response, and delay the next workflow step.
Inputs
- Topic (required) — MQTT topic used to route the request to a client.
- QoS — MQTT delivery quality level; defaults to 1 (at least once).
- Quit All — Defaults to false. When false, the required Remote Port selects the session to close. When true, closes all sessions on the client and Remote Port is not shown.
- Remote Port (required) — Session port to close when Quit All is false. The default expression reads
remote_portfrom the incoming item; use127001for the local session. - Close External Pages — Defaults to false. When enabled, also closes browser windows not opened by the automated session; this may close manually opened windows.
- Include Input Items — Defaults to false. When enabled, includes incoming item data in the request's
payload.inputItems. - Include Input Fields — Optional comma-separated field paths to copy from incoming items when Include Input Items is enabled; supports nested paths and array indexes.
- Wait For Response — Defaults to false. When enabled, waits for an MQTT response before returning output.
- Response Timeout (sec) — Maximum response wait in seconds when waiting is enabled; defaults to 60.
- Delay Next Step (ms) — Delay before continuing. Runs after the response when waiting is enabled, otherwise after publishing; defaults to
rand(200,1000).
Output shape
A single output item containing the MQTT response when waiting is enabled; otherwise the operation continues after publishing, with any configured input data included in the request payload.
The source pack shows the operation framework but omits implementation bodies, so the exact output fields and no-response return shape cannot be confirmed from the provided source.