Settings and inheritance
Settings apply through enterprise, project, Job and Task. Review the effective value and its origin before changing a local override. A saved configuration does not itself launch work or test a connection.
Override or inherit
Section titled “Override or inherit”Enable a local override for a specific resource, or return to inheritance. False, zero and empty text can be meaningful values. Structured groups can replace their inherited group as a whole; screen size is one width/height pair.
Lists and dictionaries have contribution rules. An empty local list does not necessarily clear inherited entries. Use the displayed effective view rather than guessing from the local draft.
Choose a Robot
Section titled “Choose a Robot”The current target choices are Browser, HTML, Console and Desktop Linux, subject to authorized availability. They determine action and settings support. Unsupported historical choices remain visible for repair; reading a definition does not convert them.
Browser starts with a 1280 × 720 display when no size is configured. An explicit supported size takes priority. Desktop Linux currently uses a fixed 1280 × 900 display; Console has no graphical screen. Browser-only settings do not become native desktop settings merely because a Job changes Robot kind.
Settings groups
Section titled “Settings groups”| Area | Typical use |
|---|---|
| General | Robot kind, start URL, screen size, Browser profile controls and named inputs. |
| Data | Record/file publication and available external destinations. |
| Advanced | Retry allowance/delay, User agent override and external resources. |
| Network | Headers, request filters and supported proxy settings. |
| Events | Final Session failure notifications. |
| Connectors | Named HTTP connector definitions at project level. |
Some controls move or hide for targets that cannot use them. Stored unsupported source is preserved for deliberate repair. See availability for remaining limits.
Persist profile
Section titled “Persist profile”In General, Persist profile combines its switch and Profile name on one row. When enabled, an inherited name or Default is prefilled. Typing creates a local name; clearing it returns to inheritance after save. Merely viewing the prefilled name does not create an override.
Browser profiles restore supported cookies/local storage. An explicit name can load existing state while persistence is off. Read Profiles before using the same profile concurrently.
Inputs and retries
Section titled “Inputs and retries”Named inputs initialize under params. Preserve String, Number, JSON and File types. Supported managed-secret inputs use references rather than literal credentials; do not paste their values into public examples.
Retry count means additional Attempts; delay is in milliseconds. Existing accepted Sessions keep their captured inputs and retry settings.
Current Advanced controls with demonstration values. The inactive switches indicate inheritance; enable a local override before changing that value.
Save and nested forms
Section titled “Save and nested forms”Apply in a settings collection editor updates the parent settings draft. Use the parent Save/Create command to persist it. These commands remain in the title area while fields scroll. Finish or cancel an open child editor before leaving the parent.
Revision conflicts require reviewing the latest saved state. For an uncertain acknowledgement, consult the existing operation before submitting a different request.