Execution Settings
Run Window
A run window limits when a workflow’s runs may start. Runs submitted outside it are held and start when the window opens. Configure it in the dashboard under General > Run window, or with the Run Window API. The API field isrun_window. See Run Window.
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.Retry Settings
Retry Failed Runs
allow_requeue — When enabled, the workflow is eligible for automatic retries on transient failures such as service outages and logged-out sessions. When disabled, no automatic retries occur regardless of other settings. Defaults to true.
Maximum Error Recovery Attempts
max_retries — The number of error-recovery attempts a run may use (healing, popup and logged-out recovery) and the cap on automatic requeues. Accepts values from 0 to 100. Setting it to 0 means no recovery will happen: failures are not healed or recovered and runs are not requeued. Use 0 only when no AI should touch the execution.
Only Retry Before Dry-Run Marker
deny_requeue_past_dry_run_marker — When the workflow has a dry-run marker (end_here_on_dry_run), restricts automatic retries to failures that occur before the marker. A failure at or past the marker will not be retried. If no custom error code matches the failure, the terminal error code is requeue_denied_past_dry_run_marker; otherwise the matched custom error code is kept. Defaults to true. Only effective when allow_requeue is enabled.
Captcha Settings
Manual Captcha Solve
manual_captcha_solve — When true, captchas are solved only at Captcha nodes. When false, the solver also runs before each step that acts on the page. Deprecated: automatic solving will be removed, so use Captcha nodes. The dashboard no longer shows this setting; set it through the API. A new workflow created without this field gets true. Existing workflows keep their stored value. Defaults to true.
Popup Handling
Popup XPaths
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.
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, orhttps://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.

