Skip to main content
Workflow settings control behavior that applies across all nodes and runs. You can configure these in the dashboard under the General tab of a workflow, or via the Workflow API.

​
Execution Settings

​
Recovery Toggles

These settings control which automatic recovery actions the Maintenance Agent can perform. All toggles are configurable via the dashboard (Error Handling > Maintenance Agent Settings) or the Workflow API.

​
Video Recording

video_record_session — When enabled, the agent records a video of the browser session during execution. Useful for debugging and auditing. popup_xpaths — An array of XPath selectors pointing to elements that dismiss unwanted popups (e.g., a close button on a cookie banner or promotional modal). During execution, the agent checks for these elements before and after every action (click, input text, input select, scroll, extract). If a matching element is found and visible, the agent clicks it and waits briefly for the popup to close. If a popup appears during an action (e.g., intercepting a click), the agent automatically retries the action.
Use XPaths that target the dismiss element (close button, “Accept” button), not the popup container itself.
Runtime popup recovery does not guarantee that a new XPath will be added to popup_xpaths. Eligible repeated recoveries may instead offer Adopt fix with Builder Agent from the run details page.

​
Proxy Settings

​
Proxy Setting

proxy_setting — Controls proxy behavior for the workflow. Possible values:

​
Proxy Value

proxy_value — Its meaning depends on proxy_setting:
  • "static": the target IP address; CloudCruise selects the managed proxy closest to it.
  • "country": the target country/region for proxy selection.
  • "custom": the proxy URL, e.g. socks5://user:pass@host:port, http://host:port, or https://user:pass@host:port. Stored encrypted with the workspace’s AES-256 key and re-validated against SSRF rules on every dispatch.
QUIC and WebRTC require UDP support from the selected proxy. If a SOCKS proxy does not support UDP association, browser page traffic falls back to TCP, but UDP-only WebRTC connections may not work.