> ## Documentation Index
> Fetch the complete documentation index at: https://docs.headlesslabs.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Bump Reminder

> Schedule safe reminders after verified DISBOARD bumps.

Bump Reminder detects verified DISBOARD success replies and schedules a reminder for two hours later in the channel you choose. Its local worker checks due times every 30 seconds, so normal delivery can be up to about 30 seconds after the scheduled time.

## Verified DISBOARD detection

Headless accepts only messages from the official DISBOARD bot with the positive `Bump done` marker at the beginning of the content or embed title/description. A user typing `/bump` is not enough: DISBOARD processes that external command and Headless waits for its authentic reply.

## Configuration and permissions

Configuration requires **Manage Server**. Headless needs **View Channel** and **Send Messages** in the reminder channel. The success reply can be detected in any channel in the server; the reminder is sent to the configured channel.

**1. Install DISBOARD**

Make sure the official DISBOARD bot is in the server and Headless can see its success reply.

**2. Choose a reminder channel**

Grant Headless View Channel and Send Messages in the channel where reminders should appear.

**3. Enable and test**

Run `.bumpreminder channel #reminders`, use DISBOARD's `/bump`, and check `.bumpreminder status`. The timer starts from the verified success reply.

**4. Cancel when needed**

Run `.bumpreminder off` to cancel the wait and disable detection.

### Choose the reminder channel

This setting only changes delivery; detection still waits for DISBOARD's authentic success reply.

```headless-command Syntax theme={null}
.bumpreminder channel <channel>
```

```headless-command Example theme={null}
.bumpreminder channel #reminders
```

## Timing and persistence

Each verified success replaces the previous reminder and sets its due time to two hours after the DISBOARD message timestamp. A worker checks due times every 30 seconds, so normal delivery occurs at the two-hour mark or within the following 30 seconds. State is stored per server in PostgreSQL and survives restarts. If the channel disappears, permissions are missing, or Discord rejects the send, Headless records the error and retries every 15 minutes while the feature remains enabled. A newer verified success replaces the pending schedule and resets its timer.

### Check or cancel a reminder

The root command `.bumpreminder` and `.bumpreminder status` show the current state. Use `.bumpreminder off` to cancel a pending reminder and disable detection.

```headless-command Syntax theme={null}
.bumpreminder status
```

```headless-command Example theme={null}
.bumpreminder status
```

```headless-command Syntax theme={null}
.bumpreminder off
```

```headless-command Example theme={null}
.bumpreminder off
```

> [!NOTE]
>
> The reminder text is fixed and does not mention anyone. Headless only detects DISBOARD successes and sends reminders: it does not run bumps, post automatic thank-yous, clean messages, or change channel permissions. If DISBOARD changes its success format, no new reminder is scheduled until Headless recognizes a valid reply.

> **No pending reminder appears**
>
> Check that the feature is enabled and the reply came from the official DISBOARD bot with the `Bump done` marker. User-authored messages, webhooks, and other bots are ignored.

> **The reminder could not be sent**
>
> Check `.bumpreminder status`, restore View Channel and Send Messages, and leave the feature enabled so it can retry every 15 minutes.

## Related pages

* [Giveaways](/docs/en/server/giveaways.md)
* [Messages](/docs/en/server/messages.md)
* [Headless Permissions](/docs/en/permissions.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.