CUNY Academic Commons

Hi Matt, I can confirm that the queue for that forum post was not sent out.

Boone, there is a large number of items in the wp_bpges_queued_items DB table. It goes as far back as November.

I think the time window (date_recorded comparison) for the GES health check script might need to expand from 5 minutes to 30 minutes to ensure that large sendouts are accounted for.

Anyway, I just manually pushed out immediate emails for items sent since 2020-01-31 00:00:00 GMT. Matt, can you confirm that you received the email for your forum post?

Boone, for daily digests, I attempted to use the same logic for immediate emails to force a sendout, but the arguments are different. So my script ended up sending the same daily digest to the same 27 users about 80 times according to the GES logs (massive oops!). I also noticed that the health check only accounts for immediate emails not digests. Is there a way we can write some logic for digests into the health check as well?

Thanks for looking into this, Ray.

Increasing the time-until-health-check-begins window seems OK to me. I've done so in https://github.com/cuny-academic-commons/cac/commit/9ff7d591e97a1698d49d438b95b5aa56d0f9381d.

It's also worth noting that the bpges_health_check cron event was not scheduled on the production site, and as such, the health-check code was doing nothing :) I've scheduled it, and will monitor changes.

Health check for digests is also a good idea, but it's not trivial to set up. See https://github.com/boonebgorges/buddypress-group-email-subscription/issues/163. Looking at the database, it looks like stalled digests are a very minor issue - immediates are more the problem. Let's see how the immediate health check works, now that it's actually running, and then evaluate further.