Limitations

These limitations apply as of 2026.1. If you are using an earlier version, refer to the Limitations for that specific release.

Limitations for using Perforce QAC with Validate

New versions of Validate do not support legacy QAC clients

If you try to upload or download any file using Perforce QAC 2025.3 or earlier to Validate 2025.4 or newer, a dialog will indicate that the operation fails and the client is not supported. This includes project synchronizations via QAC project analysis, where the project is connected to a Validate project.

Configurations from earlier Perforce QAC versions are also incompatible and may generate warnings in the GUI.

Existing data not viewable after migrating to or through version 2025.2

When migrating Validate from a version earlier than 2025.2 to 2025.2 or later, existing data may not be viewable after migration unless a required environment variable is set before the migration begins.

Validate performs migrations incrementally through each intermediate release version. As a result, any migration path that passes through 2025.1 → 2025.2 can trigger this issue, which was introduced in 2025.2.

This limitation does not apply if your original version of Validate is 2025.2.

Workaround:

  • If you have not yet migrated:

    Set the following environment variable before starting the migration and ensure that the Validate environment recognizes its value:

    SKIP_MIGRATE_ENTITIES_CLEANUP=true

    On Windows, this may require stopping the Validate Server and database services, setting the environment variable, and then restarting the services with the --migrate option.

  • If you have already migrated and have a backup of the original projects root:

    You can restore the backup and re‑run the migration with the required environment variable set. Note that this will revert the system to the state of the backup, and any builds, analysis results, or changes created after the original migration will be lost. This approach is recommended when a clean migration outcome is preferred and the rollback to the backup is acceptable.

  • If you have already migrated to or through 2025.2 and need to retain your builds and analysis results created after the migration:

    Contact Support for guidance and the appropriate fix utility.