TestComplete displays this message when you are trying to add a new or existing item to your test project, but the project’s or project suite’s file, or the file of one of the parent project items was changed outside of TestComplete. The addition of a new item can overwrite changes made to these files by other users. To avoid that, TestComplete re-loads the parent item or project, or the project suite and updates their state in memory (at that, TestComplete may need to close some opened editors). After that, you have to repeat adding your item anew.
Typically, this message is shown when you are working with projects bound to source control systems. Imagine the following situation: your project is stored in a source control system, and the version of the project stored in the source control is newer than the one you have on your disk. Now, suppose you are adding a new keyword test or script unit to your project. TestComplete has to add information about the new test or script unit to the project. To do that, it checks out the project file from the source control. However, the checkout operation replaces the project file on your disk with the newer version of the file from the source control. So, if TestComplete continued, your changes would overwrite changes to your project made by other users. To avoid possible issues, TestComplete cancels the addition, reloads the project and asks you to add the item once again.
See Also
Integration With Source Control Systems via SCC API Providers (Legacy)
Adding and Removing Project Items and Their Child Elements