We need to change the deduplication logic to allow us to test notification in stage on arbitrary basis.

This can be done by tweaking the deduplication logic from notification backend side.

Here they check if an event is new by extracting the deduplication key from the event.

Our deduplication key is composed here.

Implementation idea:

We could add a UUID to the payload that will be part of the deduplication key.

If deduplication logic is enabled from SWATCH side, we leave the UUID blank so it doesn't  compete to key formation.

If deduplication logic is disabled from SWATCH side, we can generate a UUID, so there is little chance to hit a duplicate.

Make sure that new changes are also reviewed by notification team.

Acceptance criteria:

• The deduplication key forming for SWATCH events in notification backend allow us to control deduplication logic enabling through the sent payload.
• The updated service is deployed on notification Stage environment.
• Test with the support script that the logic can be disabled with the payload.
• Document the payload change to facilitate SWATCH side implementation