Skip to content

Latest commit

 

History

History
31 lines (26 loc) · 1.95 KB

routine-daily-digest.md

File metadata and controls

31 lines (26 loc) · 1.95 KB

Routine notification delivery

QSL_ROUTINE_NOTIFICATION_MODE defaults to immediate. The optional daily_digest mode moves verified routine cycle and order notifications into the existing daily report. Integrate defer_routine_cycle_to_digest only at the notification boundary, after existing attention/error checks. Persist the original execution report and keep private daily-candidate production enabled. Deferral is not a Telegram delivery acknowledgement.

Unknown order outcomes, reconciliation problems, authentication failures and other operational errors remain immediate. A producer may classify an acknowledged pending order or an expected risk block as routine only with the bound evidence described in Notification routing policy. An acknowledgement does not prove a fill. Do not silence alerts because another alert was attempted, or infer success from a scheduler or CI result.

Use the existing central digest aggregator: one message containing all verified account/strategy observations for the business window. Locale is configured independently (zh-CN or en); account identity and routes come from private configuration, never repository examples. Keep unknown counts unknown and show missing/stale coverage.

Before enabling the mode for one producer, its owner must verify fresh private candidates, matching target/business day, central receipt, actual delivery, and the immediate exception path. Flag changes and deployment require owner approval. No new service, bot, database, scheduler or permissions are required.

中文:默认保持原通知方式。完成现有日报的候选、日期、覆盖和真实送达验证后, 负责人可批准一个平台切换。正常周期和已确认的常规订单进入同一份日报;订单结果 未知、对账失败及运行异常继续即时通知。待确认订单和预期风控阻断须具备上述策略 要求的绑定证据。日报使用配置的中文或英文模板。