Since a few days we are encountering issues with the sendout of email opt-in confirmations. The permission call is created like this:
PUT MarketingPermissions(ContactID='any@web.de',ContactOrigin='SAP_HYBRIS_CONSUMER',ContactPermissionID='any@web.de',ContactPermissionOrigin='EMAIL',MarketingArea='DE',CommunicationMedium='EMAIL') HTTP/1.1
Sap-Cuan-RequestTimestamp: '2021-12-20T10:43:56'
Content-Type: application/json
{
"CommunicationMedium": "EMAIL",
"ContactID": "any@web.de",
"ContactOrigin": "SAP_HYBRIS_CONSUMER",
"ContactPermissionID": "any@web.de",
"ContactPermissionOrigin": "EMAIL",
"MarketingArea": "DE",
"PermissionUTCDateTime": "2021-12-20T10:45:50",
"PermissionGranted": "Y",
"IsConfirmationRequired": true,
"PermissionNoteText": "Pre Opt-In ..."
}
The timestamp is always a very current one. E.g.
Creation Timestamp 12/20/2021, 12:02:42
Interaction Timestamp 12/20/2021, 12:02:30
I am aware that the double opt-in process does only consider interactions of probably the last minute or so. The confirmation mail is maintained:

However, only the interaction is logged but there is no further processing of the double opt-in. There is neither a outbound email or a failed one (if email not on whitelist) created.

In the application log you also see that the interaction is successfully created, but the marketing orchestrations that collect the pre opt-ins do not consider the newly created one:

Sorry for the bad quality of the picture. And the timestamp may differ a little bit to the prior ones since this screenshot was copied from another example.
I already created a ticket for SAP but maybe we can find out the reason earlier...
What I already checked:
I also do not understand why this is happening lately... Before it worked. I only changed the name of the confirmation mail (added the [...] prefix). But I would be surprised if this is a reason why the processing does not work...
So did you maybe encounter similar issues in the past? What was the reason for that?
Thank you!