Tungsten Automation Knowledge

Importing a package/ process into an environment in which they are present with higher version

000045989 · General Info · Last Updated: Sep 11, 2026

ISSUE

Problem Statement: We are experiencing a critical deployment failure where importing a package from our PROD environment into QUA.

The import wizard completes, but the process map in QUA does not updated at all (it is silently skipped / does nothing).


The Cause: We have identified that the version counter of the process map in QUA is higher than the version in the PROD package.

Because KTA strictly enforces the rule that you cannot import a lower or equal process version over an existing one, the import engine is silently ignoring the process map in the package.



SOLUTION

This is the expected behavior. Only items/artefact with higher version can be imported.


The required item can be released again or few more times until the version is higher that the environment into which it is imported to resolve the problem.



REFERENCES

Import a process

Applies to

ProductVersionBuildEnvironmentHardware
TotalAgility

Sections recovered from body HTML: issue, solution, refs.

https://aio-eus-uat-cae-aif-app14-local.redglacier-35d7ee4f.eastus.azurecontainerapps.io/article/45989 | Article 000045989 | Printed Sep 30, 2026

Back to the article · use your browser's Print command, or save the PDF.