[Bug] 自動增量報告未能產出

[lekoOwO]

发生了什么

設定了定時的增量報告，沒有收到報告

如何复现？

1. 在 Telegram 群組上設定自動增量報告

AstrBot 版本、部署方式（如 Windows Docker Desktop 部署）、使用的消息平台适配器、群分析插件版本

v4.22.0, Docker, Telegram, latest

操作系统

Linux

报错日志

[2026-03-24 23:30:00.002] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_A] [群分析插件] 开始生成增量最终报告（交错并发模式）
[2026-03-24 23:30:00.003] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_B] [群分析插件] 自动分析使用 whitelist 模式，正在扫描所有平台的群列表...
[2026-03-24 23:30:00.004] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_C] [群分析插件] auto_discover_bot_instances: 在管理器中发现 2 个平台。
[2026-03-24 23:30:00.005] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_D] [群分析插件] [群分析插件 BotManager]: Log metadata for debugging custom IDs ,Platform: telegram, Metadata Type: N/A, Metadata Name: telegram
[2026-03-24 23:30:00.005] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_E] [群分析插件] [群分析插件 BotManager]: Log metadata for debugging custom IDs ,Platform: webchat, Metadata Type: N/A, Metadata Name: webchat
[2026-03-24 23:30:00.006] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_F] [群分析插件] 发现平台 webchat 但客户端未就绪。将进行懒加载。
[2026-03-24 23:30:00.006] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_G] [群分析插件] 已创建 1 个 PlatformAdapter: ['telegram']
[2026-03-24 23:30:00.007] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_H] [群分析插件] [AutoScheduler] 正在扫描 1 个平台的群聊资源...
[2026-03-24 23:30:00.014] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_I] [群分析插件] 平台 telegram (telegram) 成功获取 2 个群组
[2026-03-24 23:30:00.014] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_J] [群分析插件] 扫码完成：共有 1 个群聊目标将执行分析任务
[2026-03-24 23:30:00.015] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_K] [群分析插件] 将为 1 个群聊生成增量最终报告 (并发限制: 4, 交错间隔: 2秒)
[2026-03-24 23:30:00.017] [Plug] [INFO] [utils.logger:25]: [report_MASKED_GROUP_2330] [群分析插件] 开始为群 -100XXXXXXXXXX 生成增量最终报告 (Platform: telegram)
[2026-03-24 23:30:00.017] [Plug] [WARN] [v4.22.0] [utils.logger:31]: [report_MASKED_GROUP_2330] [群分析插件] 群 -100XXXXXXXXXX 最终报告跳过：bot管理器未就绪
[2026-03-24 23:30:00.018] [Plug] [INFO] [utils.logger:25]: [REDACTED_ID_L] [群分析插件] 增量最终报告完成 - 成功: 0, 跳过: 1, 失败: 0, 总计: 1

你愿意提交 PR 吗？

• 是的，我愿意提交 PR!

[SXP-Simon]

感谢反馈喵，不过我一下也找不到什么问题，有时间排查一下

[SXP-Simon]

看看设置完这个以后有没有效果，这是比较简单粗暴的处理

具体的解决方案我可能还需要排查一下

[JiwaniZakir]

The key log line is 群 -100XXXXXXXXXX 最终报告跳过：bot管理器未就绪 ("report skipped: bot manager not ready"), which is the actual failure point. What's interesting is this happens on the Telegram platform despite it successfully fetching 2 groups just milliseconds earlier (log line I), meaning the platform client is functional enough to enumerate groups but the bot manager readiness check is still returning false. This points to a race condition or inconsistent state check — the code path that discovers groups and the code path that validates the bot manager before sending are likely checking different conditions or different object states. The readiness guard in the report dispatch logic (wherever bot管理器未就绪 is raised) may be too strict or checking a flag that hasn't been set yet even when the underlying client is operational.

[SXP-Simon]

The key log line is 群 -100XXXXXXXXXX 最终报告跳过：bot管理器未就绪 ("report skipped: bot manager not ready"), which is the actual failure point. What's interesting is this happens on the Telegram platform despite it successfully fetching 2 groups just milliseconds earlier (log line I), meaning the platform client is functional enough to enumerate groups but the bot manager readiness check is still returning false. This points to a race condition or inconsistent state check — the code path that discovers groups and the code path that validates the bot manager before sending are likely checking different conditions or different object states. The readiness guard in the report dispatch logic (wherever bot管理器未就绪 is raised) may be too strict or checking a flag that hasn't been set yet even when the underlying client is operational.

thanks bro, helpful analysis.

[SXP-Simon]

试试 4.9.7 看看喵

[SXP-Simon]

群友实测大概是可以的，如果不行把 debug 级别的日志发给我

[SXP-Simon]

如果没有问题我先 close 了