Page tree


The Job Info pane displays information specific to the jobs that are currently selected in the Job List pane.

The job attributes in blue are editable and can be used to affect the dispatching of a job's tasks after the job has been submitted. To edit a field with an existing value, simply click and edit. Pressing return ends the edit, and will optionally prompt you to confirm the edit. To edit an empty field, simply click in the empty area and type a new value. When fields are edited, the dashboard validates the field prior to sending to the engine.

Note that multiple jobs can be selected, and the edit will be applied to all selected jobs. If all the selected jobs have the same values for a field, that value will be displayed; otherwise, <various> will be shown.

Editable Fields

  • Tier - This field is a string representing the dispatching tier under which the job is to be scheduled. Invalid tier names will result in the job being dispatched under the default tier.
  • Priority - This field is a floating point number, generally positive. A negative priority indicates that the job is to be paused.
  • Projects - This field is a comma-separated list of strings representing the projects associated with the job. Projects are used to divide an Adaptive Farm Allocation into different shares. See Adaptive Farm Allocations for more information.
  • Crews - The crews field is a comma-separated list of crew names. The data can be entered as comma separated or space separated. Crews are used to define the combination of users and machines that are allowed to process the selected job. The crew value should match a crew defined in the crews.config file. The crew defines a list of users. A profile in the blade.config file will optionally have an Access entry defined for a crew.
  • Max Active - This is an integer representing the maximum number of concurrently active tasks that the job may have.
  • Limit Tags - The limit tags field is a comma-separated list of strings representing the tags to be associated with every command of the job. For example, an entry like "maya, shake" would cause both "maya" and "shake" limit counters to be incremented for every active command of the job.
  • Env Key - The keys field is also a list. The list contains envkeys specifying environment handlers that are added to the launch chain.
  • Service Key Expr - This service key expression is a string describing the resources required for every command of the job. More information can be found in Job Scripting Operators.
  • Metadata - The metadata is a string. This value does not affect job processing, but simply provides additional information, visible in the Job Info pane.
  • Comment - The comment field is a string. This value does not affect job processing, but simply provides additional information, visible in the Job Info pane.
  • After Jobs - This is a comma-separated list of job ids which represent the jobs that must be completed before the selected job can be considered for dispatching.
  • After Time - This is a timestamp string in the format MM/DD HH:MM:SS that represents the time after which the job may be considered for dispatching.

Job Notes

The Notes box to the right of the job attributes displays user comments and system events for the selected job. If a user has permission to add a note to a job, "click to add note" will appear below the notes area. The notes area can be resized by dragging the lower left corner of the notes box.

The system event notes are useful to show the history of the job, such as when the priority was changed or when a job was restarted.

The user generated notes could be used as a communication channel between job owners and wranglers to advise on the importance or status of a job or to exchange debugging guidance.