Cron Tasks

Cron tasks run code on a schedule — cleanup jobs, daily digests, cache pruning, etc. Each task is a file in src/cron/ exporting a Task instance.

Enable cron tasks

import { defineConfig } from "@djs-core/runtime";

export default defineConfig({
  token: process.env.TOKEN!,
  servers: ["YOUR_GUILD_ID"],
  experimental: {
    cron: true,
  },
});

Without this flag, files in src/cron/ are ignored.

Create a task

One file per task. The filename (without .ts) is the task id — hourly-cleanup.ts → hourly-cleanup.

import { Task } from "@djs-core/runtime";

export default new Task()
  .cron("0 * * * *")
  .run(async (client) => {
    console.log("Hourly cleanup…");
    // use client.db, client.guilds, etc.
  });

Cron expressions

Standard five-field syntax (minute hour day month weekday):

Uses the cron package under the hood. Expressions run in the server’s local timezone.

API

Both must be set or the task fails to register.

Dev & production

• djs-core dev — tasks in src/cron/ hot-reload with other handlers when experimental.cron is enabled.
• djs-core build — cron tasks are included in the production bundle only when the flag is on. See Bundle.

djs-core list

Lists registered cron tasks alongside commands and components.

Error handling

If a tick throws, the error is logged and the process keeps running — the next scheduled run still fires. Fix the handler; don’t let failures crash the bot.