Troubleshooting

My action changes did not reach Play

Use Apply action to validate/commit the edited form. Save is a separate operation for the complete Job. If prompted on departure, Apply action, Discard changes and Keep editing have different outcomes. Undo/Redo changes source, not past Robot effects.

A command is missing or disabled

Check the current project, your role, the resource state and any open editor with invalid fields. An administrator can review customer project access. An unavailable Robot capability cannot be enabled by changing a local label.

Toolbox is waiting for a display

Wait for the displayed readiness feedback and check any startup diagnostic. Do not launch several duplicate contexts to compensate for an uncertain response. Console has no graphical display; inspect its terminal output instead. The startup milestones show actual progress, not a start-time estimate. If the environment predates a newly available capability, explicitly close and reopen it after saving your draft and downloading needed temporary files.

A selector matches the wrong element

Inspect the current match count and order. Narrow a broad selector using stable attributes. For collection children, check inherited versus absolute context. Coordinates use the whole visible Browser display and can shift with layout changes.

A field stays empty after Type

Verify the element is editable and that your selector identifies the intended control before the click. Dynamic pages may replace elements or direct focus elsewhere. The no-locator Type variant uses current focus; use it only when the preceding actions establish that focus deliberately.

A Job works in Toolbox but fails as a Session

Save the scenario, then compare Robot kind, effective settings and launch inputs. Toolbox keeps its page and variables between commands; a Session starts fresh. Add explicit navigation, initialization and waits that your manual test had already performed.

A scenario is refused before its first action

Read the unsupported action or option diagnostic. An enabled unsupported action in an untaken branch can still cause refusal. Consult availability and repair the definition without silently discarding source.

No records appear under Data

Toolbox previews do not publish records. Its live output view is bounded and may not retain every row from a long test. A configured external-only destination is consulted there, not as a duplicate internal Data record. For an ordinary Session, check effective Push data, the destination Container, row limits and publication diagnostics. Earlier confirmed rows may remain after a later row fails.

Only one row is collected

First distinguish two limits. Track Container and DOM repetition have a default maximum of one; set a larger cap as needed. With Toolbox Debug on, outer While/Repeat On loops also advance only once per Play, even with a larger cap. Turn Debug off for a full rehearsal or deliberately advance the next iteration. Exhausted retained loops require Restart, not another unchanged Play. Ordinary Sessions traverse fully.

A temporary file disappeared

Toolbox files can be evicted as output grows, and closing/replacing the environment invalidates them. Download needed output while its command remains available. A metadata-only Preview row has no automatic persistent file behind it. Project Files are separate.

A Browser sign-in was not restored

Check the effective profile name and Persist profile setting. Enabled persistence with no name uses Default in the same project; explicit names load independently. Concurrent copies use last-valid-save behavior, not merged live state. A profile is not a full browser backup and an external site may require sign-in again.

A helper uses unexpected settings

An Internal Subsession shares caller settings/variables/target and uses the helper’s latest saved scenario. It does not initialize the helper’s own defaults. External calls use separate Sessions and cannot launch from Toolbox.

A desktop/terminal action rejects Browser fields

Console/Desktop do not support DOM locators, Browser profiles or page scripts. Desktop points are numeric and its display size is fixed. Repair incompatible inherited configuration explicitly after switching Robot kind.

A Task did not run at the expected time

Check activation, timezone, upcoming-date preview, occurrence history, overlap/catch-up choices, project dispatch and resulting Session state. A scheduled time and an actual Robot start time are different events.

Save reports a conflict or an unknown outcome

For a revision conflict, consult the latest saved definition and review differences before reapplying. For an uncertain acknowledgement, consult the existing operation using the provided controls. A second different request can create duplicate work.

A stop request is still pending

Inspect its acknowledgement and final Attempt state. Closing the display or signing out is not a Stop. Do not infer physical interruption from the request acknowledgement alone.

Report a problem

Include the business journey, approximate time, displayed status, selected Robot and a short sanitized diagnostic. If useful, include the affected Job/Session identifier through your organization’s approved support channel. Remove credentials, personal data and private target content from screenshots or sample exports. No support address is invented by this guide.