# Schedule diagnostics

<!-- Generated by docs/modules/diagnostics from the package catalogs. Write a guide in docs/diagnostics/<CODE>.md instead of editing this file. -->

Each Schedule error has a stable `code`. Its `docs` link opens the page of that code. This page lists all 52 codes, and [All diagnostics](https://vitehub.dev/docs/reference/diagnostics) lists every primitive.

## Published numbered errors

| Code | What happened |
| --- | --- |
| [`SCHEDULE_B0001`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0001) | Schedule Process Runtime driver must be "process". |
| [`SCHEDULE_B0002`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0002) | Schedule Process Runtime prefix must be a string. |
| [`SCHEDULE_B0003`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0003) | Schedule Process Runtime intervalMs must be a positive number no greater than 60000. |
| [`SCHEDULE_B0004`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0004) | Schedule Process Runtime concurrency must be a positive integer. |
| [`SCHEDULE_B0005`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0005) | \<file\>:\<line\>: \<message\> |
| [`SCHEDULE_B0006`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0006) | Schedule "\<name\>" is defined more than once:   - \<first\>   - \<second\> Rename or remove one definition. Each Schedule name must have one definition. |
| [`SCHEDULE_B0007`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0007) | Plugin \<plugin\> contributed an invalid Schedule: \<reason\> |
| [`SCHEDULE_B0008`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0008) | Schedule `cron` must map Schedule names to cron strings, such as `{ cleanup: "0 0 * * *" }`. |
| [`SCHEDULE_B0009`](https://vitehub.dev/docs/schedule/diagnostics/schedule_b0009) | Schedule Process Runtime leaseTtlMs must be a positive number. |
| [`SCHEDULE_C0001`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0001) | `defineSchedule()` requires a cron string. |
| [`SCHEDULE_C0002`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0002) | `defineSchedule()` cron must be a five-field cron expression. |
| [`SCHEDULE_C0003`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0003) | `defineSchedule()` expects an object with `cron` and `handler`. |
| [`SCHEDULE_C0004`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0004) | `defineSchedule()` does not support the "\<unknownKey\>" option. |
| [`SCHEDULE_C0005`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0005) | `defineSchedule()` requires a schedule handler. |
| [`SCHEDULE_C0006`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0006) | `defineSchedule()` timeZone needs a cron. A Schedule without cron takes its time zone from `startSchedule()`. |
| [`SCHEDULE_C0007`](https://vitehub.dev/docs/schedule/diagnostics/schedule_c0007) | \<file\>:\<line\>: `defineSchedule(cron, handler)` was removed. Write `export default defineSchedule({ cron: "...", handler })`. |
| [`SCHEDULE_DEFINITION_EXPORT_INVALID`](https://vitehub.dev/docs/schedule/diagnostics/schedule_definition_export_invalid) | Schedule "\<name\>" has no default export of defineSchedule() with a cron and a handler. |
| [`SCHEDULE_R0003`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0003) | Schedule "\<scheduleName\>" uses cron "\<cron\>", but provider wake output only supports five-field UTC cron syntax compatible with Cloudflare, Vercel, and Netlify. |
| [`SCHEDULE_R0004`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0004) | Schedule "\<scheduleName\>" must declare a static cron string for provider wake output. |
| [`SCHEDULE_R0005`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0005) | Schedule "\<name\>" and "\<existingName\>" both emit the same Vercel function path: \<safeName\> |
| [`SCHEDULE_R0006`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0006) | Schedule "\<name\>" and "\<existingName\>" both emit the same Netlify function file: \<functionName\>.mjs |
| [`SCHEDULE_R0022`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0022) | Schedule time zone could not resolve calendar fields: \<timeZone\> |
| [`SCHEDULE_R0023`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0023) | Schedule "\<id\>" must use a five-field cron expression. |
| [`SCHEDULE_R0024`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0024) | Process Schedule Runtime catchUpMs must be a finite number of zero or more. |
| [`SCHEDULE_R0025`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0025) | Process Schedule Runtime concurrency must be a positive integer. |
| [`SCHEDULE_R0026`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0026) | Process Schedule Runtime is closed. |
| [`SCHEDULE_R0027`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0027) | Cloudflare scheduled event is missing a cron string. |
| [`SCHEDULE_R0028`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0028) | Cloudflare scheduled event has an invalid scheduledTime. |
| [`SCHEDULE_R0030`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0030) | Schedule Run Attempt already exists: \<id\> |
| [`SCHEDULE_R0031`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0031) | Schedule Run already exists: \<id\> |
| [`SCHEDULE_R0032`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0032) | Schedule Run Attempt already exists: \<id\> |
| [`SCHEDULE_R0033`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0033) | Schedule Run already exists: \<id\> |
| [`SCHEDULE_R0034`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0034) | Missing schedule definition: \<name\> |
| [`SCHEDULE_R0035`](https://vitehub.dev/docs/schedule/diagnostics/schedule_r0035) | See the page of the code. |
| [`SCHEDULE_RUNTIME_CATCH_UP_INVALID`](https://vitehub.dev/docs/schedule/diagnostics/schedule_runtime_catch_up_invalid) | Schedule Process Runtime catchUpMs must be a non-negative number. |

## Operation errors

| Code | What happened |
| --- | --- |
| [`SCHEDULE_DEFINITION_NOT_FOUND`](https://vitehub.dev/docs/schedule/diagnostics/schedule_definition_not_found) | Schedule run is not available. Set manual: true on the Schedule Definition and enable Console invocation. |
| [`SCHEDULE_HISTORY_INCOMPLETE`](https://vitehub.dev/docs/schedule/diagnostics/schedule_history_incomplete) | Schedule run history is incomplete because \<recordCount\> records have no usable metadata index (maximum fallback is \<maxRecords\>). Rebuild the schedule run index before listing history. |
| [`SCHEDULE_OPERATION_FAILED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_operation_failed) | Schedule operation failed. |
| [`SCHEDULE_RUN_NOT_FOUND`](https://vitehub.dev/docs/schedule/diagnostics/schedule_run_not_found) | Schedule Run was not found. |

## Errors

| Code | What happened |
| --- | --- |
| [`SCHEDULE_INVALID_OPTIONS`](https://vitehub.dev/docs/schedule/diagnostics/schedule_invalid_options) | `startSchedule()` options are invalid: \<problem\> |
| [`SCHEDULE_NOT_FOUND`](https://vitehub.dev/docs/schedule/diagnostics/schedule_not_found) | No started Schedule has the id "\<id\>". It ran its last time, was cancelled, or never existed. |
| [`SCHEDULE_NOT_STARTABLE`](https://vitehub.dev/docs/schedule/diagnostics/schedule_not_startable) | No Schedule Definition without `cron` is named "\<name\>", so `startSchedule()` cannot start it. |
| [`SCHEDULE_OS_COMMAND_FAILED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_command_failed) | `<command>` failed with exit code \<exitCode\>: \<value\> |
| [`SCHEDULE_OS_CRON_UNSUPPORTED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_cron_unsupported) | \<value\> cannot run the cron "\<cron\>" exactly: \<reason\> |
| [`SCHEDULE_OS_INVALID_OPTIONS`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_invalid_options) | The OS timer options are invalid: \<problem\> |
| [`SCHEDULE_OS_NAME_TAKEN`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_name_taken) | \<value\> already has \<resource\>, and ViteHub did not install it as the \<scope\> timer "\<name\>". ViteHub replaces and removes only the timers that it installed. |
| [`SCHEDULE_OS_OPTION_UNSUPPORTED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_option_unsupported) | \<value\> does not support `<option>`: \<reason\> |
| [`SCHEDULE_OS_PERMISSION_REQUIRED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_permission_required) | Installing an OS timer with `scope: "<scope>"` needs root or Administrator. |
| [`SCHEDULE_OS_PLATFORM_UNSUPPORTED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_platform_unsupported) | OS timers are not supported on "\<platform\>". |
| [`SCHEDULE_OS_TIME_ZONE_UNSUPPORTED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_os_time_zone_unsupported) | \<value\> runs timers in the machine time zone "\<machineTimeZone\>", and the cron gives other runs there than in "\<timeZone\>". |
| [`SCHEDULE_STORE_FAILED`](https://vitehub.dev/docs/schedule/diagnostics/schedule_store_failed) | The store of started Schedules failed. `error.cause` has the store error. |
| [`SCHEDULE_STORE_MISSING`](https://vitehub.dev/docs/schedule/diagnostics/schedule_store_missing) | This server has no store for started Schedules. |

<!-- vitehub-docs:section-links -->
## In this section

- [Overview](https://vitehub.dev/raw/docs/schedule.md)
- [Get started](https://vitehub.dev/raw/docs/schedule/get-started.md)
- [Configure](https://vitehub.dev/raw/docs/schedule/configure.md)
- [Server API](https://vitehub.dev/raw/docs/schedule/server-api.md)
- [Hosts](https://vitehub.dev/raw/docs/schedule/hosts.md)
- [OS timers](https://vitehub.dev/raw/docs/schedule/os-timers.md)

All pages: [llms.txt](https://vitehub.dev/llms.txt)
