Manage Jobs

Create and organize

Open Jobs in a project. Create a Job with a meaningful name and description, then save it. Use labels and favorites to make frequently used Jobs easier to find. Saved views control your list presentation; they do not change scenario behavior.

Use the list’s search and filters rather than assuming that currently visible rows contain every Job. Continue to further results when available. Clear filters if a newly saved Job is not visible.

Edit metadata and scenario

Click a Job name to open Toolbox. Use its row menu for metadata and other available commands. Metadata, settings and scenario edits have separate save actions: saving one does not implicitly save another.

In Toolbox, the Save indicator shows when the current draft differs from the saved definition. Use Apply action to commit a pending action form, or Cancel to discard it. If you leave with unapplied changes, the editor asks how to handle them. Save persists the resulting scenario. The JSON source window edits the same scenario as the tree.

If another edit causes a conflict, consult the saved state before applying your changes again. Do not repeatedly overwrite a newer definition without reviewing it.

Launch

Use the Job’s launch command, review any inputs and confirm. Launching a stored Job does not save an open editor. Follow the resulting Session under Sessions.

Use a Task when the same Job needs a recurring or one-off schedule. A Job can be reused by multiple Tasks.

Import and export

Use the existing Jobs transfer commands. When importing, review validation results and the destination plan before applying. A cancelled preparation should not change saved Jobs or definitions.

Native packages can include Container and field definitions required by Track actions. The import plan distinguishes creation, reuse and compatible additions. Conflicting field types or ambiguous destinations require correction; do not guess a mapping by name.

Legacy single/array Job exports can be dropped into the existing Jobs transfer workflow for conversion. Review errors, compatibility warnings and the destination plan before applying. Warnings can identify meaningful changes, including children that now execute after their parent succeeds, converted selectors or unconfigured Subsession targets.

A file that imports successfully is not proof that it will execute unchanged. Review the resulting scenario, Robot choice and diagnostics, then test it with safe inputs. See availability.

Exports may contain authored URLs, literal values and business logic. Review their contents before sharing them. Managed secret values are not a substitute for reviewing other authored content.

Remove a Job

Use the available removal command and read its confirmation. Check dependent schedules and other references before removal. Removing a definition is separate from stopping an accepted Session and from deleting collected results.