Page MenuHomePhabricator

MassMessage not consistently delivering messages
Closed, DuplicatePublic


The last few days, we've had reports of MassMessage not delivering messages to everyone on the target list.

For T213864, two hours after the message was sent out (14:47 UTC, 16 January 2019) to a manual check shows that some of the targets have received the message, but multiple wikis have not. The queue is said to be empty.

At @IKhitron has reported messages not being delivered (seen on he.wp, where 1 user over 11 received the issue).

So far this means that some communities do not get the message that they can't edit the wikis for a short period of time tomorrow, and that others do not get the updates of technical changes, so it's a somewhat urgent problem.

Event Timeline

Probably a case of T139380: MassMessage failed delivery claiming "readonly" although the page is not protected? You should probably see the error in the local wiki's massmessage log.
(Yes, that's not super useful.)

In any case, for something as severe and sudden as a DB outage, I'd go with a centralnotice message to all logged-in editors on the affected wikis.

I've pinged @Jseddon for a CentralNotice banner, but I don't have CentralNotice admin rights myself, unfortunately.

One of the wikis reports:
14:47, 16 January 2019 Delivery of "No editing for 30 minutes 17 January" to Wikibooks:Reading room/General failed with an error code of readonly .

Yeah, we had about 440 failed deliveries.

I wonder if there's something in our code?

The only other message that failed there was again from us,
12:03, 4 October 2018 Delivery of "Reminder: No editing for up to an hour on 10 October" to Wikibooks:Reading room/General failed with an error code of readonly .

The page is getting other MMs: .

(This is also true for , FWIW.)