Creating a Template from Recurring Delivery bug

Avatar

Avatar

Darren_Bowers

MVP

Avatar

Darren_Bowers

MVP

Darren_Bowers
MVP

16-12-2020

I found a strange bug in the feature where you can create a delivery template from an existing delivery. Everything seemed to be working fine as the template was being used in a continuous delivery. However, about a week after the template was created (today) the continuous delivery threw a strange error:

17/12/2020 09:10:12 WKF-560043 Error while sending notification with delivery template 'cusMyNewTemplate'.
17/12/2020 09:10:12 DLV-490055 Failed to load delivery ID 77565251 into the cache: This delivery does not exist, has been deleted or the login does not have the required rights.

The delivery template looked fine and I could open it no problem. No rights were changed and the workflow was working 30 minutes before. I tried to duplicate it and I got the error:

WDB-200011 The requested database record does not exist.
Unable to load document of type 'Deliveries (nms:delivery)' because link 'recurringDelivery' with condition '@id = 77565251' not found in the database.

Turns out, when you create a template from another delivery, it creates a foreign key reference to the original delivery. Once the original delivery is deleted (purged), the Delivery Template ceases to function. Deleting the foreign key id seems to get the template working again.

Can anyone explain why a delivery template needs a foreign key reference to its original delivery? Seems completely unnecessary to me.

Cheers

Darren

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

craigthonis

Employee

Avatar

craigthonis

Employee

craigthonis
Employee

17-12-2020

Hi Darren,

 

So in the case of a recurring delivery, if you are creating the template based on one of the child deliveries, it would make sense that there would be some reference back to the original parent.  That said, I would see your point in thinking that logically if you duplicate (even a child delivery) and use it as a template, it shouldn't reference back to the original parent delivery.

 

On the support side, I'm fairly certain we've seen this before but was never able to isolate the root cause, so thank you for bringing this up.  I'd highly recommend submitting a ticket to Campaign Support with the repro steps and observations and this will likely end up with R&D for further review.

 

Regards,

Craig

Answers (0)