---
title: "Monitoring job run history and troubleshooting failures"
slug: "monitoring-job-run-history-and-troubleshooting-failures"
tags: ["scheduler", "job", "failures"]
updated: 2024-09-26T13:23:34Z
published: 2024-09-26T13:23:34Z
canonical: "support.lusid.com/monitoring-job-run-history-and-troubleshooting-failures"
---

> ## 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.

# Monitoring job run history and troubleshooting failures

You can examine the status of a job, who ran it, the arguments with which it ran, and more via the **History** dashboard in the [LUSID web app](https://www.lusid.com/app).

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/7e64b3a3-9b8f-4b92-b283-f51c025702e8.png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A32%3A27Z&se=2026-11-09T07%3A32%3A27Z&sr=c&sp=r&sig=gE5hv1mzbqqBX83g2dV7Iu6AJeCJiEkJGfcU7Q7LLoI%3D)

Each job run has a unique **Run ID** which you can click to examine the job results on the **Details** dashboard. On the **Details** dashboard, you can examine any arguments and environment variables passed into the job in the **Arguments** tab. If the job writes information to the console you can examine it under the **Console Output** tab:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/d2ad62ce-dcfa-4680-8514-185e4619c658.png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A32%3A27Z&se=2026-11-09T07%3A32%3A27Z&sr=c&sp=r&sig=gE5hv1mzbqqBX83g2dV7Iu6AJeCJiEkJGfcU7Q7LLoI%3D)

### Troubleshooting failed job runs

If the **Job Status** column records `Failure`, look under the **Message** column for details on the failure. If you configure a schedule to import a large volume of data, you may find the schedule fails with the following error message:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/f4dd925b-4361-4b69-8817-8a04c9b42582.png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A32%3A27Z&se=2026-11-09T07%3A32%3A27Z&sr=c&sp=r&sig=gE5hv1mzbqqBX83g2dV7Iu6AJeCJiEkJGfcU7Q7LLoI%3D) If you experience this issue, you have options for how to resolve the failure in subsequent job runs:

- You can create multiple schedules from one job, for example you could split a data import into multiple schedules, each configured with different files for import in the arguments.
- You can select **Edit Job** and change the settings in the **Limits** tab, for example you could increase the maximum time the job will run for (TTL) from 300 to 1000 seconds. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/6e14b648-30b5-4017-9f6a-d68a8b19b262.png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A32%3A27Z&se=2026-11-09T07%3A32%3A27Z&sr=c&sp=r&sig=gE5hv1mzbqqBX83g2dV7Iu6AJeCJiEkJGfcU7Q7LLoI%3D)

If you are unsure of how to resolve a failure, please [contact Technical Support](https://www.finbourne.com/contact).