Review, run and track Jobs

Check the revision, set parameters and Dataset in the Runner, start a Job and check status, details and results.

  1. Open the target Session and select a salvato script. Choose Run → Review and run.
  2. In the Runner, check the identity, version, revision, hash, source/API and parameters; scroll through the form for the other controls. Fill in the required values. You can add parameters for the single invocation and use the input and output controls when needed.
  3. Validate review checks your request without sending a Job. Only Run Job submits the execution; the revision is rechecked at the time of sending.
  4. In the Job Manager select the line to read the status and log; open the details for complete information. QUEUED means the Job is queued, PREPARING preparation, RUNNING execution and FINALIZING final stage. COMPLETED indicates completion, FAILED an error, CANCELLED a cancellation and INTERRUPTED an interrupted Job. A cancellation request may take time to reach a final state. Check details and logs even in case of error.
Runner showing parameters, Validate review and Run Job
Validate review checks the review. Run Job starts the execution.

To reopen the list, choose Run → Job Manager. In Job Manager, select the active Job, choose Jobs → Cancel running jobs and confirm. A submitted Job continues after you close the Runner or Job Manager. Selecting a record, importing, filtering and restoring a Workspace do not start a Job.

Job Manager displaying a completed script execution
Job Manager shows the execution’s identity, revision and state.
Jobs list showing PREPARING, COMPLETED, INTERRUPTED and FAILED
The State column shows the stages and outcomes of executions.
Job Manager showing a failed example Job and its details
The intentional error in this example is marked FAILED. The lower pane shows status and details. Open the execution details for the full log.

For filters, layouts and resource limits, see Manage Jobs, views and limits.

Parameters and Datasets in the Runner

The Runner shows each registered parameter with its type, whether it is required, its description and any initial value. Edit the value in the field and use Reset to restore the initial value. Validate review flags invalid entries, such as text in a double field.

To store a combination of values in the Session, enter a Dataset ID and optionally a label in Parameter Dataset, then press Save parameters as Dataset. To reuse it, enter the ID and press Load parameters; check the loaded values before running the Job. These operations do not send a Job.

Add parameter adds a valid definition only for the invocation: fill in name, type, value and, if necessary, mandatory, description, choices and limits, then Apply. The line offers Edit and Remove. The additional definition does not change the recorded parameters of the script.

Runner with a required double parameter and Dataset controls
A typed parameter and the controls for saving or loading values.

Types and fields in Add parameter

In the Add parameter module, Name identifies the value; Type chooses how to interpret it and Value is the value for this invocation. Required requires a value, Description adds an explanation. For choice, Choices is a Tcl list of alternatives, such as red blue; Minimum and Maximum indicate the limits applicable to numerical types. Apply adds the line, Cancel closes without adding it.

TypeValue to be inserted
stringText, for example hello.
integerFull number, for example 4.
doubleReal number, for example 1.5.
numberNumerical value, for example 2.5.
booleanLogic value, for example 1.
choiceOne of the alternatives stated in Choices.
colorColor, for example #112233.
pathA path.
fileA file path.
commandText of a command.

Inputs and outputs of an execution

Expand Inputs and output and choose Add input Dataset. For each row, enter an alias and optional label, and select a namespace and Dataset. Selecting a Dataset captures its revision for the request review. Remove deletes the input row. Choosing an input namespace leaves the Session’s current namespace unchanged. The selector lists Session namespaces, including empty ones and their ancestors. base includes Datasets with no explicit namespace. module groups producer namespaces, and module/<id> identifies one producer’s namespace. pending is the temporary acquisition namespace. User-created namespaces may also appear. Choose a namespace that contains the Dataset you need. Changing the namespace clears that row’s selection. If the namespace is empty, choose another one or remove the input. In Output request, you can specify an ID and label and request Replace owned output if needed. Use Validate review to check the request before selecting Run Job.