> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/settings/monitoring/scheduled-job-logs.md).

# Scheduled Job Logs

Look up the log of each run of a schedule by its Schedule ID, then preview or download it to find out why a scheduled job failed.

Under **Settings → System → Monitoring → Scheduled Job Logs**, super users browse the logs of a schedule's runs, such as a scheduled refresh or report. Tellius captures the full output of every run and keeps the 50 most recent runs of each schedule.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FSXoTVF9KZxfJHXroL4jy%2Fscheduled-job-logs-64.png?alt=media&amp;token=509cd386-1407-40a7-830e-06adadf2f357" alt="The Scheduled Job Logs page with the Schedule ID field and the Load logs button" width="563"><figcaption></figcaption></figure>

### Find the logs of a schedule

1. Type the **Schedule ID** in the field. You can enter the ID alone or in the form `dag_<id>`. Tellius removes the `dag_` prefix for you.
2. Select **Load logs**. The button is available once the field has an ID.

The list shows one row per run:

* **Run time:** when the run happened.
* **Size:** the size of its log.
* **Actions:** **Preview** and **Download**.

If the schedule has no logs, Tellius says so.

### Preview or download a log

* **Preview** opens the log in a window. For a long log, the preview shows the last 256 KB. Download the file to read the whole log.
* **Download** saves the full log file.

A log larger than 5 MB is too large to preview. Download it instead.

{% hint style="success" %}
**Troubleshooting a failed schedule.** Open the run that failed and start reading from the end of the log, where the most recent messages are. If you contact Tellius Support, download the log and attach it, with the Schedule ID and the run time.
{% endhint %}

### Who can see this page

Only super users see **Scheduled Job Logs** in Settings. A custom role reaches it with **Manage system** under **Administration**. See [Custom roles](/tellius-6.4/settings/users-and-access/custom-roles.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.tellius.com/tellius-6.4/settings/monitoring/scheduled-job-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.