# Mautic:campaigns:trigger throws Integrity Constraint Violation for Duplicate entry for key 'campaign\_rotation'

**URL:** <https://forum.mautic.org/t/mautictrigger-throws-integrity-constraint-violation-for-duplicate-entry-for-key-campaign-rotation/16713>\
**Category:** Product Support\
**Created:** [October 23, 2020, 2:17pm UTC](https://forum.mautic.org/t/mautictrigger-throws-integrity-constraint-violation-for-duplicate-entry-for-key-campaign-rotation/16713 "2020-10-23T14:17:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![codes9](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/codes9/32/682_2.png) [@codes9](https://forum.mautic.org/u/codes9)\
**Post date:** [October 30, 2020, 12:43pm UTC](https://forum.mautic.org/t/mautictrigger-throws-integrity-constraint-violation-for-duplicate-entry-for-key-campaign-rotation/16713/2 "2020-10-30T12:43:39Z")

</div>

Try  
`mautic:segment:update --force' `mautic:campaigns:update --force’

The issue refers to the ‘duplicate\_rotation’ field entry being duplicated in the database table. The data model of Mautic does not allow this. Odd that it duplicates. I suspect the previous console command you executed with cron did not complete yet when you run this one.

I notice [Integrity Constraint Violation](https://forum.mautic.org/t/integrity-constraint-violation/16731) mentioning the issue happening when cron jobs run tasks overlapping in his case. I think in this thread the issue is that a foreign key does not exist anymore / yet when the next action is triggered.

---

_[View the full topic](https://forum.mautic.org/t/mautictrigger-throws-integrity-constraint-violation-for-duplicate-entry-for-key-campaign-rotation/16713)._