Skip to content

Job details

When you click a job name on the Jobs list page, you enter the job's detail view, where you can write queries, define input variables, check status, run the job, and view results and logs. At the top of the page, you’ll see the notebook job name and status.

The page is organized into multiple tabs and panels that help you manage the job across its entire lifecycle.

  • A Query tab for viewing or managing the job query.
  • A Details tab for viewing details about the job and the cluster that the job will run on.
  • A Run History tab for viewing details about each job run.
  • A Job Status panel (collapsible) for viewing details about the job status and the available actions that you can take.
  • A rerun indicator

The following sections describe each component in more detail.

Query tab

This is the main workspace for writing, reviewing, and editing a notebook job.

It includes:

  • Query editor: Write your job in Python (PySpark) or PySpark SQL.
  • Datasets panel: View connected datasets and their schemas. Click the copy icon to insert the full dataset declaration into your query editor—this includes the function call with the dataset’s remote path, ready to use in your logic.
  • Pinned Queries panel: Access any queries you’ve pinned for this workspace and your user account.
  • Input Variables panel: Define variables that can be configured at runtime.
  • Job output area: After a run, view the Results and Logs here.

A job in the draft stage

A job in the draft stage

You can resize each panel on this tab and us it to:

  1. Browse the datasets available for analysis.
  2. Access and manage your pinned queries.
  3. Write or review a query. All members can view the query as it's being drafted.
  4. View the job results and logs (after the job has run). Only members of the job creator’s org can view logs and results.

Job management options

On the Query tab, you’ll notice a row of action buttons above the query editor. The actions available to you—for example, Submit for Review, Run Job, Accept or Decline—depend on the job’s status and your role in the workspace. The following table summarizes the options members have based on the job review or run status.

Note

You’ll find Test, Submit for Review, and Run Job in the Job Actions menu. Other available actions appear as separate buttons above the editor.

Available options by job status and role

Job status Job authors can choose ... Reviewers can ...
Draft Starter Scripts, Submit for Review, Add Input Variable, Delete / Archive Job
Under Review Cancel Review, Delete / Archive Job Accept / Decline Job
Accepted Run, Delete, Archive Job Revoke Repeatability
Queued / Running Cancel Job Revoke Repeatability
Succeeded / Failed Run Job (if rerun approved), Archive, Export Results (if job succeeded), View / Export Logs Revoke Repeatability

Note

Not all actions apply in every situation—Opaque only shows options relevant to the job’s current state. For example, Revoke Repeatability appears only after reruns are enabled. Job creators can archive a job at any point, but deletion is only allowed while the job is still in draft and hasn’t been run.

Datasets

The Datasets list displays the following information for each available dataset that you and other members can run queries on:

  • The dataset name
  • Column names and types

This list enables you to load the datasets that you want to analyze in your job query.

Pinned Queries

Pinned queries allow you to reuse useful snippets or full queries across sessions. Each pinned query is:

  • Available only to you.
  • Scoped to the current workspace.
  • Listed by oldest first, with options to copy, delete, and view.

Input Variables

You can define placeholder variables to make jobs dynamic and reusable. These variables:

  • Are defined during query authoring
  • Are filled in by the user at runtime (before job execution)
  • Appear in the Input Variables list with edit and delete options

Results and Logs tabs

When a job run completes, the following tabs are displayed below the editor:

  • Results tab:
    • Shows up to the first 100 rows of job output
    • Visible only to members of the job creator’s org
    • Includes an Export results button to download a CSV file of the results
  • Logs tab:
    • Includes output from successful runs or errors from failed runs
    • Visible only to members of the job creator’s org
    • Includes an Export results button to download a TXT file

If the job is repeatable, these tabs show the most recent run. For older runs, use the Run History tab.

Details tab

The Details tab shows basic metadata about the job:

  • Name: The job’s name (editable by the job creator). Maximum length: 50 characters.
  • Description: Optional description of the job. If you're the job creator, you can edit this field (up to 150 characters).
  • Date Created: The date and time the job was created, shown in your local timezone.
  • Created By: The email address of the member who created the job.

Run History tab

This tab lists all past executions of the job—separated into Test Runs and Job Runs. Each section displays key information for every run:

  • Date and time: Displayed in your local time zone using the US date (MM/DD/YYYY) and time (h:mm a) formats.
  • Run status: Matches the latest run status shown on the jobs list page.
  • Input variable values: If the job uses input variables, their values for each run appear in the table. You can also view the full query used for that run—especially helpful when reviewing test runs to track how your logic evolved over time.

You can click any run to view its Results and Logs, which offer the same preview and download options as those available on the Query tab.

Rerun indicator

The rerun indicator appears in the upper-right corner of the job detail page—next to the Query, Details, and Run History tabs. It shows whether reruns have been requested or approved for the job and changes depending on the job’s current status.

Job creators can request approval for reruns while drafting the job. Once submitted, all members can track the rerun status.

The following table explains what each indicator means and when it’s displayed.

Rerun indicator statuses

Indicator When displayed What it means
Request approval for reruns Draft The job creator can check this box before submitting the job for review.
Awaiting approval Under Review All members can see that reruns were requested and are pending approval.
Approved for rerun Accepted Reruns are allowed. This appears only if approval was requested during the draft stage.

Note

This feature is not available in single-member workspaces.

Job Status panel

The Job Status panel is a collapsible sidebar that tracks the job’s progress from creation to completion. Think of it as your running summary for where the job stands and what actions have been taken.

It includes the following sections:

  • Job created (query status): Shows whether the query is still being drafted or ready for review and execution. If test runs have been performed, their status is also displayed here—helping reviewers understand whether the job logic has been validated using synthetic data.
  • Job approval (review status; multiparty workspaces only): Displays each member’s decision—Pending, Accepted, or Declined—along with any comments they provided during review. All comments remain visible for reference.
  • Job execution: Updates when a job is run, showing when it was executed and how long it took to complete.