Dashboard name

Allows users to enter the dashboard name to search for related subscriptions.

Push method

Allows users to search for related subscriptions based on the push method.

• Lark, Lark group
• WeCom, WeCom group
• Webex, Webex group
• Email, email group
• DingTalk, DingTalk department group, DingTalk regular group
• General IM
• Webhook

Push status

Users can search for relevant subscriptions based on push status. The following provides a detailed explanation of the different status types:

• In progress: The subscription task has been triggered and is currently pushing data to the target channels, but the entire process has not yet been completed.
• Success: The subscription task has completed the push according to the configured rules, and the data has been delivered in full and successfully to all target channels or recipients.
• Partial success: The subscription task involves multiple push targets. Some targets have been pushed successfully, while others have failed (for example, insufficient permissions for certain group chats or invalid email addresses).
• Failure: The subscription task did not complete the push, and none of the target channels or recipients received the data.
• Waiting for retry: The push task failed on its first execution, but the system has triggered the automatic retry mechanism and is currently waiting for the next retry attempt.
• Push timeout waiting: When user data is ready and enters the push process, but the push is not successfully executed due to reasons such as screenshot failure, the system displays this status. This status has a default duration of 10 minutes. If the data is still not pushed within 10 minutes, the system will automatically change to "Push failure" status and send relevant notifications to the user.
• Waiting for readiness: The subscription task has been created, but the required data is not yet ready. The system is waiting for the data source to become ready, and the push process will begin once the data is prepared.
• Waiting for data readiness timeout: The data was not ready within the specified task day, so the system has stopped waiting. This subscription task will no longer continue to push, and it usually needs to be retriggered or the data source checked.
• In queue: The push task has been submitted, but due to system resource limitations or a high number of current processing tasks, the subscription is in a waiting queue to be scheduled for execution. It will be processed automatically when the system becomes idle.
• Waiting for first push: The subscription task is ready but the first push has not yet been triggered. It is in the waiting stage before the scheduled push time or trigger condition is met.

Task start time

The time when this subscription task instance starts execution.

Trigger type

Indicates the startup method for this task instance: scheduled trigger or manual trigger.

Status

The current stage of the task instance in the push process.

Action

Terminate the push for a task that is in progress.
Click the terminate push button in the action column. After secondary confirmation, you can terminate the push process for the current task instance.

Dashboard page

• When there are multiple sheet pages in the dashboard, you can specify to push only certain sheet pages.
• When pushing multiple sheet pages or all pages, a screenshot of each sheet page will be taken and combined into a single push message.
• The number of sheet pages selected determines the number of page screenshots in the push message.

Based on bookmark

• The dashboard allows users to save the current dashboard view as a bookmark. The subscription feature allows users to select bookmark content to push as the subscription content.

Quick bookmark

• This feature is supported when users create a new subscription, but not when editing a subscription.

Subscription title

You can modify the subscription title and choose to include the date. If selected, the subscription title will display the date (for example: "2025-07-08 My subscription title").

Note

You can add a note to the subscription.

• You can modify the text font
• You can insert hyperlinks
• You can insert images
• You can mention recipients (when the push method is Lark or Lark group)

Content

You can select the access method for the subscription dashboard.

• Dashboard access link
• Dashboard screenshot "full-size image" / dashboard screenshot "thumbnail image" / dashboard PDF download link

Remarks

Supports setting remarks for the dashboard. The configured remarks will be displayed at the end of the subscription push message. Supports remark text or hyperlinks, and allows modification of font formatting.

• Screenshot time: If the dashboard screenshot or dashboard PDF download link is not selected in the content options, this option will not be available.
• Subscription management link

Subscription time

• Scheduled: Supports scheduled push. When scheduled push is set, the system will take a dashboard screenshot and push it at the specified time.
  • Supports daily, weekly, and monthly pushes.
  • Supports custom scheduling by trading day, working day, or every day.
• Triggered when data synchronization is completed.
  • Extracted datasets support this feature (in the privatized version, direct connection datasets support implementation via data readiness configuration).
  • If the data synchronization completion time is later than the scheduled push time, the system will wait until data synchronization is completed before pushing.

Push language

• Supports modifying the language type of the push subscription message.
• If 'Auto' is selected, the system will detect the current language setting and push according to the language type configured during subscription.

Push method

• Supports modifying the push method for the subscription: Lark, Lark group, WeCom, WeCom group, Webex, Webex group, email, email group, DingTalk, DingTalk department group, DingTalk regular group, generic IM, Webhook.

Recipient

• Supports modifying the recipient/channel for the subscription.
• When the push method is set to group, you need to set the permission reference user, that is, whose permissions the push content is based on.
  • For example, if a chart in the dashboard has row-level permissions configured for its dataset, selecting different permission reference users may result in different data being pushed.
  • After setting the permission reference user, the referenced user will receive a notification.

Exception handling

• If there are chart anomalies in the dashboard, do not send: If any chart in the dashboard has no data, query failure, or query timeout, the dashboard screenshot message will not be sent to the recipient.
• Automatic retry after failure: If the push fails, the system will automatically attempt to resend after 1 hour.
• If any chart in the dashboard has empty data, do not send.
• The maximum data delay for subscription tasks is 48 hours: When the subscription time is set to "trigger when data synchronization is complete", if data synchronization is never completed after the subscription task trigger waiting begins and the delay exceeds 48 hours, the subscription task will terminate waiting and will no longer execute the push.

Subscription modification notification

• If the subscription is modified, it can be pushed to the recipient or to the creator.
• Subscription modification notifications include information about subscription creation, modification, and deletion.

Subscription failure notification

Supports configuring notification recipients for subscription execution failures. You can choose to push to the creator or customize the push to specified Lark users or Lark groups. When selecting Lark, multiple recipients can be configured; when selecting Lark groups, multiple group chats can be added, and the bot must first be added to the corresponding group chat.