How to debug Newsletter Studio during sending emails?

Questions
,
1

Is there a way to debug the NS at the point of sending emails?

We construct a list of EmailReceiver and they seem to be correct but GetDataModel is not getting hit for some list providers and the report shows 0 recipients despite the list returned containing the correct list of EmailReceiver.

Just to give an example of logs from GetReceiversForList:

This list GetDataModel’s hits correctly and emails are sent:

Receiver: EmailReceiver { Identifier: EmailReceiverIdentifier { ProviderPrefix: “subscribersAffiliatesByLastPasswordChange”, Identifier: “77135” }, Email: “…”, Name: “Han Omar” }

Provider Prefix: “subscribersAffiliatesByLastPasswordChange”; ListId: “member|Affiliate|en-GB|passwordChange:null”; Subscribers: 18; Receivers: 18

This list never hits GetDataModel for any subscriber and 0 emails are sent:

Receiver: EmailReceiver { Identifier: EmailReceiverIdentifier { ProviderPrefix: “subscribersClientsWithPromoCode”, Identifier: “23486” }, Email: “…”, Name: “Dell” }

Provider Prefix: “subscribersClientsWithPromoCode”; ListId: “subscriber|user|en-GB|promocode:newsletter-form”; Subscribers: 48; Receivers: 48

We have several lists that are working correctly and several that are not working. Any idea what to check/ log to investigate the issue? Currently, we do not have any means of debugging the sending stage, why the recipients from the list are selected for email and not receive emails.

We do not know whether this is an issue with the upgrade because in lower versions of Umbraco and NS, the sending was working. Or this is our implementation issue. Anyway, how to debug the sending stage?

Thanks

Versions

Umbraco version 17.2.2

Newsletter Studio version 17.0.6

2

@markusjoha

3

Hi @ewuski ,

Adding a debugging issues link. Please check:

Hope it helps!

4

Hi!

I think that the problem might in the length of the prefix, the identifiers would become very long and might not fit into the db-column.

Can you double check the logs (trace logs) when the sending queue is created, check the length of you identifiers and ensure that they fit into the db column.