Run your first job

A short tutorial. You'll save a query, reference it from a job, run the job, and inspect the result. This is the simplest end-to-end path — save SQL once, run it on demand.

For the full lifecycle — scheduling, versioning, debugging — see the Jobs section.

Prerequisites

• A cluster in Running state. See Quickstart.
• A catalog. See Connect a catalog.

1. Save a query

1. Open Queries in the sidebar and click Create query.

2. Enter a Name — e.g. row-count.

3. Pick your Catalog.

4. Paste a simple statement against a table in your catalog:

   SELECT COUNT(*) FROM my_table;

5. Click Save.

You now have a reusable, named SQL statement. For more on queries (sharing, tags, editing), see Queries.

2. Create a job that runs the query

1. Open Jobs in the sidebar and click Create job.
2. Enter a Name (e.g. hello-lakesail) and pick a Team.
3. Choose SQL as the job type.
4. For the source, pick Saved query and select row-count from step 1.
5. Leave the compute defaults in place and click Save.

The job now references your query. If you ever edit the SQL, the next run picks it up automatically — no job redeploy.

3. Run it

From the job's detail page, click Run now. A new job run moves through its lifecycle (pending → starting → running → succeeded). On a warm cluster, most runs reach succeeded in under a minute.

4. Inspect the result

Click into the run to see logs, metrics, and the query output. Runs are immutable records — re-running creates a new run rather than modifying this one.

Next

• Schedule the job so it runs automatically.
• Set up notifications so you hear about failures.
• Read about queries for sharing, tagging, and reuse patterns.
• Read about runs and debugging if a run doesn't behave.