Skip to content

Notebook jobs

Notebook jobs let you write and run encrypted Python or SQL queries within a secure workspace. They are ideal when you need custom logic, flexible data processing, or workflows that aren’t easily handled through the no-code interface.

To open a notebook job, click its name on the Jobs page. The job detail view includes three main tabs:

  • Query: View and edit the job’s code
  • Details: View job and cluster information
  • Run History: View previous runs and results

A collapsible Job Status panel on the right shows the current status and available actions. The rerun indicator above the panel shows whether reruns have been requested or approved, and updates based on the job’s status.

The following sections describe each part of the page in more detail.

Query tab

The Query tab is the main workspace for writing, reviewing, and editing a notebook job.

It includes:

  1. Query editor: Write your job in Python (PySpark) or PySpark SQL.
  2. Query panels:
    • Datasets: View connected datasets and their schemas. Use the copy icon to insert a dataset declaration into the editor.
    • Input Variables: Define variables that can be configured at runtime.
    • Pinned Queries: Access queries you’ve saved for this workspace.
  3. Job status: Shows the current job state and actions taken.
  4. Job output area: Displays results and logs after a run.

Screenshot of a job awating approval for rerun

You can resize panels to suit your workflow. From this tab, you can:

  • Browse available datasets
  • Access and manage pinned queries
  • Write or review a query (visible to all members during drafting)
  • View results and logs after execution (visible only to members of the job creator’s organization)

Job management options

The Query tab includes action buttons above the editor, including a Job Actions menu. Available actions—such as Submit for Review, Run Job, Accept, or Decline—depend on the job’s status and your role (author or reviewer).

The table below summarizes available actions by role and job status.

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

Info

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 panel lists all datasets available for analysis, including:

  • Dataset name
  • Column names and types

Use this panel to to load the datasetsinto your query.

Input Variables

Input variables let you make jobs dynamic and reusable. They:

  • Are defined during query authoring.
  • Are set at runtime before execution.
  • Appear in the Input Variables panel with edit and delete options.

Pinned Queries

Pinned queries let you reuse query snippets or full queries across sessions. Each pinned query:

  • Is available only to you.
  • Is scoped to the current workspace.
  • Can be copied, viewed, or deleted.

Results and Logs tabs

After a job run completes, the following tabs appear below the editor:

  • Results:
    • Displays up to the first 100 rows of output.
    • Visible only to members of the job creator’s organization.
    • Includes an option to export results as a CSV.
  • Logs:
    • Shows output from successful runs or errors from failed runs.
    • Visible only to members of the job creator’s organization.
    • Includes an option to export logs as a TXT file.

If the job is repeatable, these tabs show the most recent run. Use the Run History tab to view earlier runs.

Details tab

The Details tab shows basic metadata about the job:

  • Name: Editable by the job creator (maximum 50 characters)
  • Description: Optional, editable by the job creator (maximum 150 characters)
  • Date created: Displayed in your local timezone
  • Created by: The email address of the job creator

Run History tab

The Run History tab lists all past executions, grouped into Test Runs and Job Runs. Each entry includes:

  • Date and time (local timezone; U.S. format: MM/DD/YYYY, h:mm a)
  • Run status
  • Input variable values (if used)

You can also view the full query used for each run, which is helpful when tracking changes during testing.

Click any run to view its results and logs, with the same preview and export options available on the Query tab.

Rerun indicator

The rerun indicator appears in the upper-right corner of the job detail page. It shows whether reruns have been requested or approved and updates based on the job’s status.

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

The following table describes each indicator state.

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 a job’s progress from creation to completion.

It includes:

  • Job created (query status): Indicates whether the query is in draft or ready for review and execution. Test run status is also shown.
  • Job approval (review status): Displays each member’s decision (Pending, Accepted, or Declined) along with any comments.
  • Job execution: Shows when the job was run and how long it took.