> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-4.md).

# Planner tables

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/viewpoint-4.md).
{% endhint %}

## Description

Planned and repeating tasks (schedules), their logs, and the schedule categories.

## Tables

| Name                                                                                                        | Columns | Comment                                                                                                                                                                                                                                                                                                                                                                                                              | Type       |
| ----------------------------------------------------------------------------------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| [enum\_ScheduleCategory](https://docs.snapfix.com/engineering-reference/db/tables/enum_schedulecategory.md) | 8       | The schedule categories schedule and tasknotif, code in uuid. The scheduler also uses duedatenotif, which has no row \[[ASK-246](https://github.com/snapfix/docs/blob/main/ASK.md#ask-246-should-the-enum-lookup-tables-follow-the-code-or-be-retired)]. No code reads the table \[[ASK-246](https://github.com/snapfix/docs/blob/main/ASK.md#ask-246-should-the-enum-lookup-tables-follow-the-code-or-be-retired)]. | BASE TABLE |
| [schedule](https://docs.snapfix.com/engineering-reference/db/tables/schedule.md)                            | 19      | One v2 recurring schedule (schedule JSON, task template JSON, trigger times), run by py\_scheduler's v2 scheduler; schedule\_v3 rows with sch\_version v2 read their details from here.                                                                                                                                                                                                                              | BASE TABLE |
| [schedule\_bug\_v2](https://docs.snapfix.com/engineering-reference/db/tables/schedule_bug_v2.md)            | 19      | Copy of the schedule table (same columns), no row newer than 2021-10; no in-scope code refers to it \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                                                                                                                                        | BASE TABLE |
| [schedule\_log](https://docs.snapfix.com/engineering-reference/db/tables/schedule_log.md)                   | 10      | One task the v2 scheduler created, with the schedule (uuid\_schedule), the template task (uuid\_JobOrigin), the new task (uuid\_JobNew) and the schedule and task JSON.                                                                                                                                                                                                                                              | BASE TABLE |
| [schedule\_log\_v3](https://docs.snapfix.com/engineering-reference/db/tables/schedule_log_v3.md)            | 10      | One task the v3 scheduler created, with the schedule (uuid\_schedule), the template task (uuid\_JobOrigin), the new task (uuid\_JobNew) and the JSON used. No code deletes rows; about 12.9 GB on staging.                                                                                                                                                                                                           | BASE TABLE |
| [schedule\_nfc02](https://docs.snapfix.com/engineering-reference/db/tables/schedule_nfc02.md)               | 19      | Copy of the schedule table (same columns), no row newer than 2021-10; only a migration names it \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                                                                                                                                            | BASE TABLE |
| [schedule\_v3](https://docs.snapfix.com/engineering-reference/db/tables/schedule_v3.md)                     | 24      | One recurring schedule or task notification, linked to a task, with its schedule and task JSON, trigger times, time zone and paused state; py\_scheduler runs it.                                                                                                                                                                                                                                                    | BASE TABLE |

## Relations

```mermaid
erDiagram


"enum_ScheduleCategory" {
}
"schedule" {
}
"schedule_bug_v2" {
}
"schedule_log" {
}
"schedule_log_v3" {
}
"schedule_nfc02" {
}
"schedule_v3" {
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# 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://docs.snapfix.com/engineering-reference/db/tables/viewpoint-4.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.
