---
title: "Scheduler.Job.HistoryWithLogs"
slug: "schedulerjobhistorywithlogs"
tags: ["scheduler", "provider", "jobs"]
updated: 2024-08-21T13:24:42Z
published: 2024-08-21T13:24:42Z
canonical: "support.lusid.com/schedulerjobhistorywithlogs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduler.Job.HistoryWithLogs

| **Type** | **Read/write** | **Author** | **Availability** |
| --- | --- | --- | --- |
| [Data provider](/v1/docs/what-are-a-data-provider-and-a-direct-provider) | Read | Finbourne | Provided with LUSID |

The `Scheduler.Job.HistoryWithLogs` provider enables you to write a [Luminesce SQL query](/v1/docs/understanding-the-luminesce-sql-query-syntax) that retrieves job run history, including console output logs, from [Scheduler](/v1/docs/scheduler).

> **Note:** The LUSID user running the query must have sufficient [access control permissions](/v1/docs/creating-policies-to-control-access-to-providers-for-different-luminesce-end-users) to both use the provider *and* read Scheduler job run history data. This should automatically be the case if you are the domain owner.

**See also:** [Scheduler.Job](/v1/docs/schedulerjob), [Scheduler.Job.History](/v1/docs/schedulerjobhistory)

## Basic usage

```sql
select * from Scheduler.Job.HistoryWithLogs where <filter-expression>;
```

## Query parameters

`Scheduler.Job.HistoryWithLogs` has parameters that enable you to filter or refine a query.

To list available parameters, their data types, default values, and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, ParamDefaultValue, Description from Sys.Field where TableName = 'Scheduler.Job.HistoryWithLogs' and FieldType = 'Parameter';
```

## Data fields

By default, `Scheduler.Job.HistoryWithLogs` returns a table of data populated with particular fields (columns). You can return a subset of these fields.

To list fields available to return, their data types, whether fields are considered 'main', and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, IsMain, IsPrimaryKey, SampleValues, Description from Sys.Field where TableName = 'Scheduler.Job.HistoryWithLogs' and FieldType = 'Column';
```

> **Note:** Fields marked 'main' are returned by queries that include a caret character, for example `select ^ from Scheduler.Job.HistoryWithLogs`.

## Examples

> **Note:** For more example Luminesce SQL queries, visit our [Github repo](https://github.com/finbourne/luminesce-examples/tree/master/examples).

### Example 1: Retrieve console output logs for a particular job

```sql
select Logs from Scheduler.Job.HistoryWithLogs where JobScope = 'transactions' and JobCode = 'upsert-transactions'
```

### Example 2: Retrieve console output logs for a specific job run

```sql
select * from Scheduler.Job.HistoryWithLogs where RunId = 'f77b5b02-7f03-417d-a46c-5b3a0ee094f2'
```

### Example 3: Retrieve failure message and output logs for failed runs

```sql
select RunId, Message, Logs from Scheduler.Job.HistoryWithLogs where JobStatus = 'Failure' limit 20
```

### Example 4: Retrieve logs for all failed jobs in a job scope

In this example, `Scheduler.Job.HistoryWithLogs` is joined with [Scheduler.Job](/v1/docs/schedulerjob) to retrieve all console output logs for failed jobs within a particular scope.

```sql
select *
from Scheduler.Job.HistoryWithLogs h
join Scheduler.Job j
  on h.JobScope = j.JobScope
  and h.JobCode = j.JobCode
where h.JobStatus = 'Failure'
and j.JobScope = 'transactions'
```