Hey Mark,
I’m currently looking into this and trying to figure out what’s going on. What @sam pointed out is true—best_replies not including the last post could cause the job to stall. I’m about to wrap up a fix for that and introduce a fail-safe to turn the job into a no-op and log an error if there’s a bug in the query. This is not ideal and it shouldn’t happen, but it’s better than regenerating the same summary over and over again.
On the other hand, I’m looking at the Franklin Lexington... example you shared, which I suspect is a different issue because:
- It already has a summary (
149). UPPER(ais.content_range) < t.highest_post_number + 1should beFALSE.UPPERshould return109, which equalshighest_post_number + 1.
The end of the content_range interval would need to be lower for the job to stall due to that. We don’t really care about hidden or deleted posts when deciding if a summary is outdated; we only want to avoid summarizing those.
Do you have ai_summary_gists_enabled enabled? If so, can you confirm that you have two summaries for that topic, one with type 0 and one with type 1? Also, in the ai_api_audit_logs query you shared, what is the value in the feature_name column?
I’ll keep you updated with what I find.