GREAT LOTUS PYAUTO WEB icon

GREAT LOTUS PYAUTO WEB

10 action groups: ManagerAction, MouseAction, KeyboardAction, BrowserControl, ElementAction, ImageAction, OthersAction, EmailAction, DeveloperAction, General Debug

7. Others → cancel_alert

AI-generated

Summary

Publishes an MQTT request asking the client to cancel the browser’s current alert, confirm, or prompt dialog. Set the required Topic and Remote Port to route the request; optionally keep the dialog visible before cancellation, forward selected input fields, wait for a response, and delay the next workflow step.

Inputs

  • Topic (required) — MQTT topic used to publish the request to the client.
  • QoS — MQTT delivery quality level: 0 (at most once), 1 (at least once), or 2 (exactly once). Defaults to 1.
  • Include Input Items — When enabled, attaches selected fields from incoming items to payload.inputItems. Defaults to false.
  • Include Input Fields — Comma-separated field paths to include from incoming items, such as id,name or status.detail. Applies when Include Input Items is enabled.
  • Wait For Response — When enabled, waits for the MQTT response before returning output. Defaults to false.
  • Response Timeout (sec) — Maximum wait time for a response, in seconds. Defaults to 60; shown when waiting is enabled.
  • Delay Next Step (ms) — Delay before the workflow continues. Defaults to rand(200,1000); runs after the response if waiting, otherwise after publishing.
  • Remote Port (required) — CDP port used to route the command to the correct browser session. Defaults to the incoming remote_port value; use 127001 for a local session.
  • Show (sec) — How long the dialog remains visible before the client clicks Cancel, in seconds. Defaults to 0 for immediate handling.

Output shape

A response-derived output when waiting is enabled; otherwise the operation proceeds after publishing, with any included input data carried in the request.

The operation publishes a cancel-alert request over MQTT. The response and output details depend on the client response and node execution behavior.

Links

Discussion