Supervise Sessions
Open Sessions for the selected project. Use filters and continuation controls to find the relevant execution. Optional auto-refresh updates the active list; loading more results can suspend that refresh so the list remains usable.
Read an execution
Section titled “Read an execution”Open a Session to review its inputs, effective settings, ordered Attempts, logs and control feedback. A Session is the execution request; an Attempt is one actual run in that request’s history.
| Situation | What to check |
|---|---|
| Accepted or queued | Whether the project can dispatch work and capacity is available. |
| Starting | Whether startup completes or reports an error. |
| Running | Current action, logs and available display. |
| Pause requested | The acknowledgement; a request is not proof of a paused Robot. |
| Waiting to retry | The recorded retry allowance and delay. |
| Finished | Final outcome, earlier Attempts and saved outputs. |
Use the state and diagnostic actually displayed. A successful launch acknowledgement means the request was accepted, not that the Job has completed.
Cancel, stop, pause and resume
Section titled “Cancel, stop, pause and resume”Cancel applies to work that has not started where the command is available. Stop requests interruption of the active Attempt. Pause and resume have their own request and acknowledgement state.
After issuing a control, inspect its result. Do not infer that closing a window, signing out or losing the display stops the Robot. Stopping does not undo an external form submission or remove records already confirmed.
Retries and manual relaunch
Section titled “Retries and manual relaunch”The retry count is the number of additional Attempts. A count of three allows the initial Attempt plus up to three retries. Each retry starts the scenario again using the original effective inputs; there is no failed-action checkpoint resume.
Design repeated external actions carefully. A form submission may have succeeded before a later error. Review the target system before relaunching work that can create duplicates.
Manual relaunch is available only for eligible states. Active work cannot simply be duplicated through relaunch. Voluntary stop or cancellation is separate from automatic failure retry.
Logs and results
Section titled “Logs and results”Filter logs to the relevant Attempt, level or action before downloading. If the UI reports a download-size limit, narrow the selection. Inspect Data for internally confirmed records and Files for published output. Configured external-only results live at their selected destination. Toolbox previews and temporary downloads remain separate.
Retained action/log history can rotate oldest entries when its limits are reached. Inspect any history bounds or partial-output indicators; the visible view is not a promise of an unbounded transcript. External Subsessions have their own execution history and can continue after the parent completes.
Grouped commands show per-item outcomes. A partial result does not mean that every selected Session changed. If a response is uncertain, consult the existing operation or Session before creating a new request.
Remove history
Section titled “Remove history”Read the history-removal confirmation, including its scope. Protected active work cannot be removed through ordinary history cleanup. History removal does not mean that external effects, collected records or independent files are undone.