We are experiencing an issue in which the software is not recognizing entities i

...alling the entity that exists.

Any suggestions why any new object changes in a Data store are now causing these alerts?

By the way, I am running the process as Sys Admin so security should not be a factor.

What about security for your database? Has the user credentials changed? How about the user rights in the database?

Karla - When you go into the DataStore and click Verify, does the green "Entities Verified" show or the red? Also, if you run impact analysis on the datatype, does anything come back as being "out dated"?

Alex- as sys admin, it should not matter about credentials to the data store in Appian. We'v confirmed with our DBA and through a test using our Appian Service Account that nothing has changed as far as rights for this account. Meaning, I logged in via another IDE outside of Appian and ran an insert statement to the same table that the model was trying to write to via Appian, and my manual insert was successful.

Christine - now that's an interesting question. Yesterday, when all of this was happening....I added an entity, clicked very and publish and instead of getting pink (to add the table to the database), it was green. I logged into our database outside of Appian, and the table did not exist. Yesterday, Appian would not create a new table via the verify and publish. We did a reboot, and after that when I added a new entity to a datastore, Appian showed pink and added the new table.
I am still trying to run impact analysis on the impacted CDTS and continuously receive a server timeout. We just did a reboot so I am hoping to get this answered for you shortly.

Christine - I failed to mention, that in an effort to resolve this issue, I took it upon myself to import a copy of the Data Store and all CDTs from our test environment back into our Dev environment...so I am no longer working with the corrupted database. That could be a factor now...anyway, I ran Impact Analysis and nothing required updating.