Configuration and administration
Have an Agent send analysis reports on a schedule
Set analysis tasks and execution times to send reports to Feishu or email on a schedule.
Guide · Module: integrations · Developers · Deployment: Not specified · Confirmed product versions: Not specified · Source: Existing documentation
Scheduled analysis reports are an Agent automation capability: the system executes a natural-language analysis on schedule, sends conclusions to a Feishu group or email, and keeps a run record and corresponding conversation. Feishu or Slack channels let users ask questions and receive bot replies; scheduled reports run on schedule and send results one way. Channel integration and scheduled report notification methods are configured separately. Connecting a Slack channel does not add a Slack scheduled notification option.
Before you begin
- Permissions: your project role must be “Project owner” or “Project administrator.”
- A data Agent that can answer questions independently and already has data sources attached.
- A delivery target: a Feishu group bot Webhook URL or a list of email recipients.
- Decide the analysis time range and metric definitions, and include them in the instructions.
- Entry: left main navigation → “More” → open target Agent → top “Scheduled tasks” tab.
Steps
Create a task and fill in the four core fields
The empty state in “Scheduled tasks” shows No scheduled tasks and prompts you to create one so the Agent runs and sends results automatically on schedule. Click “New scheduled task” to open the creation dialog. This step has only four fields:
| Field | Required | Description |
|---|---|---|
| Name | Yes | Placeholder such as Daily active user analysis; up to 255 characters |
| Description | No | Placeholder suggests a brief description of the task's purpose; up to 1024 characters |
| Instructions | Yes | Placeholder suggests telling the Agent what to do, such as analyzing yesterday's orders and outputting key metrics |
| Frequency | Yes | Presets: “Every 10 minutes,” “Every 30 minutes,” “Hourly,” “Daily,” “Weekly”; after selection, guidance says it uses the current device timezone |
State the time range, metrics, grouping dimensions, and output format clearly for consistent periodic results. For comparisons such as “same period last week,” also specify the data cutoff time.
Add a notification method
A new task is Disabled by default and has no notification method. Open its details/edit form and choose one of two methods:
- “Feishu Webhook”: enter a Webhook URL, with placeholder
https://open.feishu.cn/open-apis/bot/v2/hook/.... - “Email”: enter an address in Recipients and press Enter to add it, one at a time.
Until a method is selected, the section shows Notifications not configured.
Trigger once manually, then enable
After saving, click “Trigger now” to run once. A message says it is queued and can be viewed in history later. Open “View history” and confirm the conclusions and format match expectations.
Once verified, turn on the enable switch. Enabling without a notification method prompts you to configure one first.
Clicking “Trigger now” on a disabled task first shows a Task not enabled prompt explaining that confirmation will enable the task and then trigger execution immediately. The confirmation button is “Enable and trigger.”
Check the next trigger and run history
Task entries show the next trigger time and, after one run, the previous trigger time. Enabling or changing frequency recalculates the next trigger to a future time; it is not picked up immediately. Use “Trigger now” to run immediately.
“View history” opens run history named after the task. Each record is Running, Success, Execution failed, or Notification failed; with no records, it shows No run records. Records with conclusions have “View conversation” to return directly to that run's conversation.
Allow recipients to unsubscribe
Email footers and Feishu card endings include “Unsubscribe,” opening the unsubscribe page. Recipients first see a confirmation question and the associated Agent. After confirmation, the page shows Unsubscribed and the task becomes Disabled. Invalid links show a message to reopen from an email or Feishu message.
Key constraints
| Item | Value or default | Where to change it |
|---|---|---|
| State after creation | Disabled | Enable switch in task details/edit form |
| Minimum execution interval | 10 minutes | Frequency in task form |
| Notification method | Not configured by default; one must be selected before enabling | Task details/edit form |
| Name limit | 255 characters | Task form |
| Description limit | 1024 characters | Task form |
| Timezone | cron is interpreted in UTC; the editor converts from your current device timezone | Frequency in task form |
| Report language and timezone | Use the project owner's current preferences; changes apply to the next execution | Language and timezone in user settings |
| Missed periods | No historical backfill; align to the next future time only | No UI switch |
| Feishu delivery retries | Exponential backoff, up to 4 attempts; retry only rate limits and network/5xx errors, while content or signature errors fail immediately | No UI switch |
| Tables in Feishu cards | Up to 3 Markdown tables in reports (Feishu cards allow 4) | Constrain output in instructions |
| Unsubscribe link validity | 90 days | No UI switch |
| Conversation type | Tasks generate scheduled conversations, filterable by “Scheduled tasks” in “All conversations” | No UI switch |
Troubleshooting
| Symptom | Identifying condition | Resolution |
|---|---|---|
| No delivery at the scheduled time | No run record, and next trigger time is incorrect | Confirm the task is not Disabled; changing frequency or recently enabling recalculates the next trigger to a future time |
| History status is Execution failed | The record has no conclusion, only failure status | Reproduce the same question in web “Conversations” first, then check data sources and model groups |
| History status is Notification failed | The record has conclusions, but recipients received nothing | Check Webhook URL or recipient validity, SMTP availability, and whether the Feishu group bot is still present |
| Enabling prompts you to configure notifications first | Notification method still says Not configured | Select “Feishu Webhook” or “Email,” complete the fields, then enable |
| Runs missed while disabled are not resent | Those periods have no records in history | Expected behavior; historical periods are not backfilled. Use “Trigger now” for immediate verification |
| Feishu delivery reports too many tables | Report has more than 3 Markdown tables | Instruct “Output at most 3 tables and list the rest as bullet points” |
| Unsubscribe says the link is invalid and must be reopened from an email or Feishu message | Link is over 90 days old, or task was deleted | Click from the latest report; a deleted task needs no unsubscribe |
| Recipients receive reports with incorrect times | Report timezone differs from expectations | Project owner changes timezone in user settings; the next execution uses it |
Next steps
- Let users actively ask questions in messaging tools: Connect a Feishu bot · Connect a Slack bot
- Open trends and details whenever needed: Dashboards
- Find task conversations and conclusions: Conversations