This usually happens when something in the project gets modified during the test run. When TestExecute exits and detects unsaved changes, it tries to open the “Save changes” dialog. In silent mode the dialog cannot be shown, so the log records “Tried to open the Save dialog. The default value: YES”, but the attempt still causes TestExecute to return exit code -1, which makes Jenkins mark the build as failed.
Since you mentioned it only happens with one project, it’s very likely that something in that project is being updated at runtime. Common causes are Name Mapping auto-updates, scripts changing project variables, or any code/extensions that modify project configuration files.
A simple way to confirm is to run the project once in UI mode and close TestExecute/TestComplete afterward. If it asks you to save the project or suite, then something was modified during execution. You can also compare the project files before and after a run to see which file changed.
Most often the fix is disabling automatic Name Mapping updates or ensuring the tests do not persist changes to project variables or project configuration files during execution. Once the project finishes a run without being marked as modified, the save prompt will not be triggered and the exit code should return to normal.
If this resolves your scenario, marking it as the solution helps future readers find it quickly.
