Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Delivery failed while sending out campaigns

Avatar

Avatar
Validate 10
Level 3
priyankah586599
Level 3

Likes

23 likes

Total Posts

89 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 3
priyankah586599
Level 3

Likes

23 likes

Total Posts

89 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
priyankah586599
Level 3

22-03-2018

Hi,

I see the following error, popping up in many of my campaigns. But when I recreate the delivery , it's sent out successfully. What could be the reason?

1449115_pastedImage_0.png

Regards,

Priyanka

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 3
kapilsharma0101
Level 3

Likes

14 likes

Total Posts

52 posts

Correct Reply

18 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Validate 1
Level 3
kapilsharma0101
Level 3

Likes

14 likes

Total Posts

52 posts

Correct Reply

18 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
kapilsharma0101
Level 3

22-03-2018

This error occured due to the "Duplicate Key Value Constraint". It means that it was trying to insert the same Primary Key in the nmsMirrorPageInfo schema which was already existing.

So, you can just copy the delivery and try to send it again, it should work this time. If still this is not working then you have to remove the same primary keys from concerned table manually.

Reason For Same Primary Key Generation :

There is only one sequence in adobe campaign named "xtknewid" which generates the primary keys for all the schemas except broadlog and tracking logs. And there is a limit on the sequence that is can generate so and so number of primary keys in one iteration. When these all primary keys of one iteration are exhausted, it creates second iteration and starts to generate the same primary keys.

But, as it inserts primary keys in all the schemas, there is a very very less chance that duplicate primary key can enter in the same table in which it was previously inserted.

This is exactly what happened here. Hope I cleared your doubt.

Answers (1)

Answers (1)

Avatar

Avatar
Validate 10
Level 3
priyankah586599
Level 3

Likes

23 likes

Total Posts

89 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 3
priyankah586599
Level 3

Likes

23 likes

Total Posts

89 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
priyankah586599
Level 3

22-03-2018

Hi Kapil,

Yes that was a detailed note. Thank you very much

Regards,

Priyanka