https://community.appian.com/discussions/f/general/2292/hello-we-are-posting-messages-to-the-tempo-news-feed-via-the-smart-serviceHello, we are posting messages to the Tempo news feed via the smart service in one of our processes and came across a situation where the ID of the post was repeated with two different process instances. Has anyone come across this? Is there a limit beforeen-USTelligent Community 12https://community.appian.com/thread/8093?ContentTypeID=1Thu, 13 Mar 2014 03:56:11 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:90bf10cb-5401-4096-a8cc-9c114bcaee23Eduardo FuentesYou may also want to run a &quot;describe&quot; in the database of the tp_feed_entry table to make sure the structure hasn&#39;t been changed by somebody. The ID needs to be auto-increment and the primary key (unique)<div style="clear:both;"></div>https://community.appian.com/thread/8092?ContentTypeID=1Thu, 13 Mar 2014 03:50:54 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:16cc5a6c-46f5-4e45-8143-ccb287590c6eEduardo FuentesUnless this environment is pointing or was pointing to the wrong primary ds at some point<div style="clear:both;"></div>https://community.appian.com/thread/8091?ContentTypeID=1Thu, 13 Mar 2014 03:50:30 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6a425c4b-0d25-4fc3-ad8a-a68dd812231cEduardo FuentesCan you post an example of the repeated ID? The part you see after the letter (e.g. 103534 for e-103534) is a primary key in the Primary Data Source so it cannot be duplicated.<div style="clear:both;"></div>