Ask on a schedule and email the answer
An AI scheduled task combines a prompt, schedule, recipients, answer language, and optional LLM. The platform asks the model at the scheduled time using the assistant's platform-query tools, stores the answer, and sends it by email. Examples include daily status summaries, weekly effectiveness reviews, and periodic degradation checks.
Tasks do not modify resources or parameters. Results depend on the prompt, available records, and model. Scheduled questions do not replace continuous alert rules.
Create a task
Ask in chat: “Every Monday at 9, email me the usage status of all modules.” The assistant reports the schedule and next run. The current user must have an identity and valid email; chat-created tasks send only to that user's own address, regardless of other recipients in the prompt.
Use /tasks to list your tasks. Administrators manage all tasks under AI configuration → Scheduled tasks, including prompts, schedules, recipients, language, activation, and models. They can run a task immediately and inspect each answer.
Schedules and timezones
Schedules use the platform timezone, UTC+8 by default. The examples below assume UTC+8. The minimum interval is one hour, each user may have 20 tasks, and prompts are limited to 2000 characters.
| Schedule | Meaning |
|---|---|
0 9 * * 1 | Every Monday at 09:00. |
0 8 * * * | Every day at 08:00. |
0 9 1 * * | The first day of each month at 09:00. |
@every 24h | A 24-hour interval, rather than a fixed daily clock time. |
Check the displayed next run before saving. Missed historical slots are not replayed individually: an overdue task runs once after recovery, then advances to a future slot. A task still running skips the next occurrence to avoid overlap.
Configure email
Configure SMTP in System management → System parameters, under notifications. Tasks send through the platform notification channel.
| Parameter | Purpose |
|---|---|
notify.email.host / port | SMTP server and port. |
notify.email.security | starttls, tls, or none, matching the server. |
notify.email.username / password | Login credentials; passwords are encrypted and masked. |
notify.email.from | Sender address. |
notify.email.skip_verify | Whether to bypass server certificate verification. |
notify.email.timeout_seconds | Connection and delivery timeout. |
Password authentication is sent only over encrypted or local connections. Email is currently plain text with Markdown retained as text.
Runs and retries
Runs use the task center. Inspect answers, tools read, recipients, and delivery status. Retries reuse an existing answer rather than asking again, and recipients already sent successfully are not resent on a retry of the same job.
For missing mail, check activation and next run, the selected or default model, task-center errors, SMTP, and recipient addresses. Configure missing models or email channels before retrying.