Dynamics 365 Marketing – So Much Noise

its too noisy

In all companies I have contracted for, the monitoring of the health of Dynamics 365 CE has been vital.
CE has bugs and so do the custom developments (plugins , power automate, workflows).

Thus on a regular basis, the plug-in logs and system jobs are monitored for any issues.

Issue
What would happen if a Microsoft plug-in starts reporting plug-in errors erroneously.
Well, this has occurred with the following plug-in:

Microsoft.Dynamics.Crm.MarketingPlugins.Plugins.Data.MktActivityCreatePostEventPlugin

Error states (summary):
Exception ‘InvalidPluginExecutionException’ occured: Failed to create activity of type ‘task’. Customer journey iteration entity doesn’t exist for the customer journey with ID and iteration number ‘1’. This is likely to be a transient error, a retry in some minutes may help.

Impact

The impact is moderate to high, as the error is continuously repeating and it is a furfy. This
limits the automation of weekly check to a certain extent. So is the error a furfy?



YES IT IS – according to Microsoft

Marketing product group has confirmed that this should not have any impact to your system. The error is coming from our marketing plugin for creating CRM Activities (Task, Phone call, Appointment) or Custom channels.

Before creating the entity record, this plugin performs a “RetrieveMultiple” request to Dataverse to make sure that the customer journey iteration exists. In most of the cases it does, but sometimes “RetrieveMultiple” returns empty list, and this results in an execution error (which is then automatically retried later, and the retried attempt is almost always successful).

The reason for the “RetrieveMultiple” returning an empty list is usually caused by a race condition, new journey starts be processed but it has not been yet created on Dataverse side, this is a rare but possible case to occur.


RACE Condition:
A race condition that is continually failing. Is that an error. Not according to Microsoft,
Marketing product group has confirmed that this should not have any impact to your system


WOW – and that’s not a good wow!!!

The question that should be asked and answered by MS:
why is this being experienced repeatedly.