I created a model to automate the database management tasks for our enterprise database. It works great, however I had one glaring oversight. The first step is to reconcile and post the versions. I have the option checked to abort if conflicts are detected. I was thinking that would make the model stop as well, but apparently that isn't the case. The model proceeds to roll through the warning message, delete the (unreconciled) versions, compress, analyze and rebuild indexes. I just realized this when I lost about two hours of edits because of this. Lol. Not a huge deal because we have hourly backups, but surely there must be a way to configure this to abort on a warning message, right?
.png "MatthewBeal"){kind=avatar}
