Links

Scheduler API

The Scheduler API gives apps the possibility of creating tasks that run in a defined schedule. It can be a one-time event or a recurring task. It uses agenda.js as the backend, so the schedule syntax and internal processes are all according to its documentation.
See the details on the API in the Module scheduler definition. There's also an example app that can be used as a guide.

Add permissions

As per the Permission System, the Schedule API needs the following permission in your app's manifest (app.json file):
{
permissions: [
{ "name": "scheduler" }
]
}

Register jobs (processors)

To use the Scheduler API you'll need two things:
  • The functions to be run as jobs (we call them processors).
  • The schedule in which they run.
This is configured in the app's extendConfiguration method. During the app's startup, the processors are registered to make them available for scheduling.
1
public async extendConfiguration(configuration: IConfigurationExtend) {
2
configuration.scheduler.registerProcessors([
3
{
4
id: 'first',
5
processor: async (jobData) => console.log(`[${ Date() }] this is a task`, jobData),
6
},
7
]);
8
}
The processor is an async function and can receive arguments (jobData). The arguments are passed during scheduling.

Start a job

To trigger the registered processor as a job, you must provide:
  • The id of the processor.
  • The type of job it will be. The available types are scheduleRecurring (the job runs in an interval) and scheduleOnce (the job runs once using the when keyword).
Starting a job can be done when running a slash command, for example:
1
// slashcommand class
2
public async executor(context: SlashCommandContext, read: IRead, modify: IModify): Promise<void> {
3
// SCHEDULING A RECURRING TASK
4
const task = {
5
id: 'first',
6
interval: '10 seconds',
7
data: { test: true },
8
};
9
await modify.getScheduler().scheduleRecurring(task);
10
11
// SCHEDULING ONETIME TASK
12
const task = {
13
id: 'first',
14
when: '8 seconds',
15
};
16
await modify.getScheduler().scheduleOnce(task);
17
}
You can also trigger a job as soon as it gets registered, without the need for manual or automated triggering. When you register your processor in the extendConfiguration method, you can pass a prop called startupSetting in the processor's object:
1
import { StartupType } from '@rocket.chat/apps-engine/definition/scheduler';
2
// ...
3
4
configuration.scheduler.registerProcessors([
5
{
6
id: 'first',
7
processor: async (jobData) => console.log(`[${ Date() }] this is a task`, jobData),
8
startupSetting: {
9
type: StartupType.ONETIME,
10
when: '20 seconds',
11
data: { test: true },
12
}
13
},
14
{
15
id: 'second',
16
processor: async (jobData) => console.log(`[${ Date() }] this is a task`, jobData),
17
startupSetting: {
18
type: StartupType.RECURRING,
19
interval: '20 seconds',
20
}
21
},
22
]);
This indicates that you want that particular processor to be scheduled as soon as it is registered. You can define the "immediate scheduling" as a recurring job (StartupType.RECURRING) or a one-time job (StartupType.ONETIME). You can also pass data using the data object. It will work just like when you schedule a task using the modify accessor.
Here, data is not something that's passed to the processor or a function as a living object or executable code. This data is a static piece of data that is passed to the processor's first argument.
The signature of the processor function is as follows:
(jobContext: IJobContext, read: IRead, modify: IModify, http: IHttp, persis: IPersistence) => Promise<void>
The first argument is the data object you're passing when actually scheduling the job; ([k: string]:any). The rest of the arguments are passed when the function is run.

Cancel a job

To stop a job, all you have to do is pass the ID of the job you want to stop:
const jobId = 'first';
await modify.getScheduler().cancelJob(jobId);
It will stop the running job (if any).

Cancel all jobs from the app

To stop all the current running jobs from the app:
await modify.getScheduler().cancelAllJobs();
Last modified 3mo ago
Rocket.Chat versions receive support for six months after release.