## Usage
### On Demand
```ruby
user = User.first
user.notification.text "You'll receive this after 1 minute"
user.notification.scheduled(Time.now + 1.minute)
```
#### Send bulk
```ruby
users = User.all
users.each do |user|
user.notification.text "This is an important announcement"
user.notification.template "main/announcement", {announcement_id: 1}
user.notification.scheduled(Date.tomorrow.to_time)
end
```
### Reply
```ruby
@reply.text "This is a reminder"
@reply.text "Take the cookies out of the oven"
@reply.scheduled(Time.now + 30.minutes)
```
## Params
Name
Description
send_at Time
Required.
The date and time when message(s) will be sent.
tag Symbol
Optional. Scheduled message identification tag, can be any symbol.
## Daemon
To send scheduled messages, there is a process that must be running. It can be started as follows:
### In Background
```bash
kogno scheduled_messages start
```
### In Foreground
```
kogno scheduled_messages fg
```
### With the others processes from Kogno
```
kogno start
Kogno 1.0.0 server starting in production
Http: starting daemon..
Sequence: starting daemon..
Scheduled Messages: starting daemon..
```
## Deleting and Re-Scheduling
If the tag argument has been included in the creation of a scheduled message, as the example bellow:
```ruby
user = User.first
user.notification.text "This is a 24 hours reminder."
user.notification.scheduled(Time.now + 24.hours, :window_24h)
```
Then the following methods of the `User` model can be called:
### `destroy_scheduled_messages(tag=Symbol)`
Deletes the scheduled message associated with the provided tag.
```ruby
@user.destroy_scheduled_messages(:window_24h)
```
### `reschedule_message(tag=Symbol)`
Re-Schedule the messages associated with the provided tag.
```ruby
@user.reschedule_scheduled_message(:window_24h, Time.now + 23.hours + 55.minutes)
```
### `scheduled_message?(tag=Symbol)`
Checks if there is a scheduled message associated with the provided tag.
```ruby
@user.scheduled_message?(:window_24h)
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.kogno.io/scheduled-messages.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.