Jobs API

Last Updated: July 2022

The Jobs API provides a way for your app to run asynchronous tasks (meaning that after starting a task you don't have to wait for it to finish before moving on). As an example, you may need to run a simulation that takes a long time (potentially hours or days) to complete. Using the Jobs API you can create a job that will submit the simulation run, and then leave it to run while your app moves on and does other stuff. You can check the job's status at any time, and when the job is done the Jobs API will help retrieve the results.

Job Management Software

The Jobs API leverages third-party job management systems to perform the actual execution of the jobs, including HTCondor and Dask. HTCondor is well suited for executing long-running executable-like jobs, such as running a simulation. Dask is ideal for converting existing Python logic into efficient, parallel running code, especially logic that uses the SciPy stack to perform the analysis.

To learn more about HTCondor and Dask, review the following resources:


A scheduler is the part of a job managment system that is responsible for accepting job requests and assigning them to the appropriate computing resources to be executed. The Jobs API needs to know how to connect to the scheduler to be able to submit jobs. This is done by adding Scheduler entries in the Tethys Portal admin pages (see: Tethys Compute Admin Pages: Schedulers).


Schedulers can also be created and accessed programmatically using the lower-level compute API. However, this approach is only recommended for experienced developers (see: Low-Level Scheduler API).

Scheduler App Settings

Apps that use either HTCondor or Dask should define one or more app Scheduler Settings in their app class. Tethys Portal administrators use this setting to assign an appropriate Scheduler to the app when it is being configured. To access Schedulers assigned to app Scheduler Settings, use the get_scheduler() method of the app class. See Scheduler Settings for more details.

Job Manager

To facilitate interacting with jobs asynchronously, the metadata of the jobs are stored in a database. The Jobs API provides a Job Manager to handle the details of working with the database, and provides a simple interface for creating and retrieving jobs. The Jobs API supports various types of jobs (see Job Types).

Using the Job Manager in your App

To use the Job Manager in your app you first need to import the TethysAppBase subclass from the module:

from .app import App

You can then get the job manager by calling the method get_job_manager on the app.

job_manager = App.get_job_manager()

You can now use the job manager to create a new job, or retrieve an existing job or jobs.

Creating and Executing a Job

To create a new job call the create_job method on the job manager. The required arguments are:

  • name: A unique string identifying the job

  • user: A user object, usually from the request argument: request.user

  • job_type: A string specifying on of the supported job types (see Job Types)

Any other job attributes can also be passed in as kwargs.

# create a new job from the job manager
job = job_manager.create_job(
    name='myjob_{id}',  # required
    user=request.user,  # required
    job_type='CONDOR',  # required

    # any other properties can be passed in as kwargs
        os.path.join(app_workspace, ''),
        os.path.join(app_workspace, 'input_1'),
        os.path.join(app_workspace, 'input_2')

# properties can also be added after the job is created
job.extended_properties = {'one': 1, 'two': 2}

# each job type may provided methods to further specify the job
job.set_attribute('executable', '')

# save or execute the job
# or

Before a controller returns a response the job must be saved or else all of the changes made to the job will be lost (executing the job automatically saves it). If submitting the job takes a long time (e.g. if a large amount of data has to be uploaded to a remote scheduler) then it may be best to use AJAX to call the controller that executes the job in the background.


The Jobs Table Gizmo has a built-in mechanism for submitting jobs with AJAX. If the Jobs Table Gizmo is used to submit the jobs then be sure to save the job after it is created.

Common Attributes

Job attributes can be passed into the create_job method of the job manager or they can be specified after the job is instantiated. All jobs have a common set of attributes. Each job type may have additional attributes specific that are to that job type.

The following attributes can be defined for all job types:

  • name (string, required): a unique identifier for the job. This should not be confused with the job template name. The template name identifies a template from which jobs can be created and is set when the template is created. The job name attribute is defined when the job is created (see Creating and Executing a Job).

  • description (string): a short description of the job.

  • workspace (string): a path to a directory that will act as the workspace for the job. Each job type may interact with the workspace differently. By default the workspace is set to the user's workspace in the app that is creating the job.

  • extended_properties (dict): a dictionary of additional properties that can be used to create custom job attributes.

  • status (string): a string representing the state of the job. Possible statuses are:

    • 'Pending'

    • 'Submitted'

    • 'Running'

    • 'Results-Ready'

    • 'Complete'

    • 'Error'

    • 'Aborted'

    • 'Various'*

    • 'Various-Complete'*

    • 'Other'**

    *used for job types with multiple sub-jobs (e.g. CondorWorkflow). **When a custom job status is set the official status is 'Other', but the custom status is stored as an extended property of the job.

All job types also have the following read-only attributes:

  • user (User): the user who created the job.

  • label (string): the package name of the Tethys App used to created the job.

  • creation_time (datetime): the time the job was created.

  • execute_time (datetime): the time that job execution was started.

  • start_time (datetime):

  • completion_time (datetime): the time that the job status changed to 'Complete'.

Job Types

The Jobs API is designed to support multiple job types. Each job type provides a different framework and environment for executing jobs. When creating a new job you must specify its type by passing in the job_type argument. Supported values for job_type are:

  • 'BASIC'



  • 'DASK'

For detailed documentation on each of the job types see:

Retrieving Jobs

Two methods are provided to retrieve jobs: list_jobs and get_job. Jobs are automatically filtered by app. An optional user parameter can be passed in to these methods to further filter jobs by the user.

# get list of all jobs created in your app

# get list of all jobs created by current user in your app

# get job with id of 27

# get job with id of 27 only if it was created by current user
job_manager.get_job(job_id=27, user=request.user)


Be thoughtful about how you retrieve jobs. The user filter is provided to prevent unauthorized users from accessing jobs that don't belong to them.

Jobs Table Gizmo

The Jobs Table Gizmo facilitates job management through the web interface and is designed to be used in conjunction with the Job Manager. It can be configured to list any of the properties of the jobs, and will automatically update the job status. It also can provide a list of actions that can be done on the a job. In addition to several build-in actions (including run, delete, viewing job results, etc.), developers can also create custom actions to include in the actions dropdown list. The following code sample shows how to use the job manager to populate the jobs table:

job_manager = App.get_job_manager()

jobs = job_manager.list_jobs(request.user)

jobs_table_options = JobsTable(
    column_fields=('id', 'name', 'description', 'creation_time', 'execute_time'),
    actions=['run', 'resubmit', '|', 'logs', '|', 'terminate', 'delete'],

See also

Jobs Table

Job Status Callback

Each job has a callback URL that will update the job's status. The URL is of the form:


For example, a URL may look something like this:

The output would look something like this:

{"success": true}

This URL can be retrieved from the job manager with the get_job_status_callback_url method, which requires a request object and the id of the job.

job_manager = App.get_job_manager()
callback_url = job_manager.get_job_status_callback_url(request, job_id)

API Documentation

Job Manager

class tethys_compute.job_manager.JobManager(app)

A manager for interacting with the Jobs database providing a simple interface creating and retrieving jobs.


Each app creates its own instance of the JobManager. The get_job_manager method returns the app.

from .app import App

job_manager = App.get_job_manager()
create_job(name, user, groups=None, job_type=None, **kwargs)

Creates a new job of the given type.

  • name (str) -- The name of the job.

  • user (django.contrib.auth.User) -- A User object for the user who creates the job.

  • groups (django.contrib.auth.Group, optional) -- A list of Group object assigned to job. The job will be saved automatically if groups are passed in. Default is None.

  • job_type (TethysJob) -- A subclass of TethysJob.

  • **kwargs --


A new job object of the type specified by job_type.

get_job(job_id, user=None, filters=None)

Gets a job by id.

  • job_id (int) -- The id of the job to get.

  • user (django.contrib.auth.User, optional) -- The user to filter the jobs by.


A instance of a subclass of TethysJob if a job with job_id exists (and was created by user if the user argument is passed in).

get_job_status_callback_url(request, job_id)

Get the absolute url to call to update job status

list_jobs(user=None, groups=None, order_by='id', filters=None)

Lists all the jobs from current app for current user.

  • user (django.contrib.auth.User, optional) -- The user to filter the jobs by. Default is None. This parameter cannot be passed

  • other. (cannot be passed together with the user parameter. Choose one or the) --

  • groups (django.contrib.auth.Group, optional) -- One or more Group objects to filter the jobs by. Default is None. This parameter

  • other. --

  • order_by (str, optional) -- An expression to order jobs. Default is 'id'.

  • filters (dict, optional) -- A list of key-value pairs to filter the jobs by. Default is None.


A list of jobs created in the app (and by the user if the user argument is passed in).

Tethys Job

class tethys_compute.models.TethysJob(*args, **kwargs)

Base class for all job types. This is intended to be an abstract class that is not directly instantiated.

exception DoesNotExist
exception MultipleObjectsReturned
property cached_status

The cached status of the job (i.e. the status from the last time it was updated).

Returns: A string of the display name for the cached job status.

execute(*args, **kwargs)

executes the job


Check if it is time to update again.


True if update_status_interval or longer has elapsed since our last update, else False.

Return type:


abstract pause()

Pauses job during execution

process_results(*args, **kwargs)

Process the results.

property process_results_function

Returns: A function handle or None if function cannot be resolved.

abstract resume()

Resumes a job that has been paused

property status

The current status of the job. update_status is called to ensure status is current.

Returns: A string of the display name for the current job status.

It may be set as an attribute in which case update_status is called.

abstract stop()

Stops job from executing

property type

Returns the name of Tethys Job type.

update_status(status=None, *args, **kwargs)
Updates the status of a job. If status is passed then it will manually update the status. Otherwise,

it will determine if _update_status should be called.

  • status (str, optional) -- The value to manually set the status to. It may be either the display name or the three letter database code for defined statuses. If it is not one of the defined statuses, then the status will be set to OTH and the status value will be saved in extended_properties using the OTHER_STATUS_KEY.

  • *args -- positional arguments that are passed through to _update_status.

  • **kwargs -- key-word arguments that are passed through to _update_status.

property update_status_interval

Returns a datetime.timedelta of the minimum time between updating the status of a job.

Low-Level Scheduler API


Gets a list of all scheduler objects registered in the Tethys Portal


List of Schedulers


Gets the scheduler associated with the given name


name (str) -- The name of the scheduler to return


The scheduler with the given name or None if no scheduler has the name given.

tethys_sdk.compute.create_scheduler(name, host, scheduler_type='condor', **kwargs)

Creates a new scheduler of the type given.

  • name (str) -- The name of the scheduler

  • host (str) -- The hostname or IP address of the scheduler

  • scheduler_type (str) -- Type of scheduler to create. Either 'dask' or 'condor'. Defaults to 'condor'.

  • kwargs -- Keyword arguments of scheduler-specific options. See: create_dask_scheduler and create_condor_scheduler.


The newly created scheduler


The newly created scheduler object is not committed to the database.

tethys_sdk.compute.create_condor_scheduler(name, host, username=None, password=None, private_key_path=None, private_key_pass=None)

Creates a new condor scheduler

  • name (str) -- The name of the scheduler

  • host (str) -- The hostname or IP address of the scheduler

  • username (str, optional) -- The username to use when connecting to the scheduler

  • password (str, optional) -- The password for the username

  • private_key_path (str, optional) -- The path to the location of the SSH private key file

  • private_key_pass (str, optional) -- The passphrase for the private key


The newly created condor scheduler


The newly created condor scheduler object is not committed to the database.

tethys_sdk.compute.create_dask_scheduler(name, host, timeout=None, heartbeat_interval=None, dashboard=None)

Creates a new dask scheduler

  • name (str) -- The name of the scheduler

  • host (str) -- The hostname or IP address of the scheduler

  • timeout (str, optional) --

  • heartbeat_interval (str, optional) --

  • dashboard (str, optional) --


The newly created dask scheduler


The newly created dask scheduler object is not committed to the database.