Thank you so much _Manoj_Kumar! 9 rows of data were somehow removed from the XtkNewID table when I imported the new schemas and I had to manually add them back to the table to resolve the errors.

It looks like the primary id sequence for this table is reset to 0 after my schemas import (the schemas were for new custom tables and did not have any changes made to any out of the box schemas). How do I reset this primary key to start from the latest value + 1?.

We recently upgraded to build 9032 and tonight was the first time I imported database schema from our test instance into our production instance. The import was successful without any errors, however, after the import all my workflows and campaigns started throwing this error. Has anyone encountered...