Investigate situation where notification responses for an abonnement aren't created and notifications to a subscriber aren't being sent

[alextreme]

Thorough analysis from my end in Taiga DH 585, using Open Notificaties 1.5.1

In short, there seem to be a (small) number of cases where notifications aren't being sent as expected.

[joeribekker]

Refinement: Alex didnt reproduce this but was able to verify that some subscribers did not receive a notification at all, while some did. This also differed per event (where all subscribers did get a notification).

So, somewhere Open Notifications somehow skips sending to a subscriber.
93 cases were recorded over a few thousand records. Alex suspects it has something to do with RabbitMQ.

Joeri: Can we investigate what happens if a Celery task crashes? Does it still create a record? Or is the record simply not created at all. Maybe SSL errors that cause a connection to not return a HTTP response code?

[joeribekker]

Estimate: Investigating 1 week

@JanBrek @PeterVanBragt please approve.

[PeterVanBragt]

Is it possible to monitor missing outbound notifications? Maybe because of updates of components this issue is not occurring anymore? (discussed with Alex during POD meeting)
Maybe the current productie data can be analysed to check if this is still occuring?
Let's also check with Jan B (back from holiday next week)