Notification service queries for a Subscription with
notificationId during the /push-handlers/records-changes workflow. This call from Notification service to the Register service fails if the notificationId contains upper case characters. The reason being, we are lower casing the notificationId before querying Register service, which will return an empty list because its not an exact match.
This issue was observed with the test subscription with notificationId
testingAcknowledgement in our environment.
Unless there is a specific reason we are lowercasing the notificationId, we can remove it.