automation/schedule/page.mdx

---
title: "Command: `schedule`"
short_name: schedule
---

import Modes from "@/components/MDX/Modes";

# `schedule`

Sends a message after the given timeframe.

## Notes

If you don't specify a unit of time like s, m, h, etc, it will default to seconds. So if you put 100 by itself, it will put it down as 100 seconds.

### Syntax

```
-schedule <time_interval> [content]
/schedule content: [content] time_interval: [time_interval] channel: [channel] (OPTIONAL)
```

### Required Permissions

`ManageMessages`

### Modes

<Modes modes={["legacy", "interaction"]} />

### Examples

```
-schedule 20m Code that one file you need to make!
/schedule time_interval: 20m content: Code a file! channel: general
```
1	rakinar2	575	---
2	rakinar2	626	title: "Command: `schedule`"
3	rakinar2	575	short_name: schedule
4			---
5
6			import Modes from "@/components/MDX/Modes";
7
8			# `schedule`
9
10			Sends a message after the given timeframe.
11
12			## Notes
13
14			If you don't specify a unit of time like s, m, h, etc, it will default to seconds. So if you put 100 by itself, it will put it down as 100 seconds.
15
16			### Syntax
17
18			```
19			-schedule <time_interval> [content]
20			/schedule content: [content] time_interval: [time_interval] channel: [channel] (OPTIONAL)
21			```
22
23			### Required Permissions
24
25			`ManageMessages`
26
27			### Modes
28
29			<Modes modes={["legacy", "interaction"]} />
30
31			### Examples
32
33			```
34			-schedule 20m Code that one file you need to make!
35			/schedule time_interval: 20m content: Code a file! channel: general
36			```