Below you will find the most common causes of issues involving project activation in the XTM Cloud UI.
Issue description & Solution
There is a timeout in the browser
The activation of large projects can take a while and can usually result in timeouts in the browser.
Solution: Usually, you just need to clicks on the Wait button a few times to activate the project. In some cases, clicking the Wait button produces no visual results but the process is initiated in the background and is completed after some time; if you access the UI after a couple of minutes, the project is active.
Do not click the Activate button too many times, as this will cause permanent issues for a specific project.
API users: use the updateProjectActivity method to activate your projects and bypass cumbersome UI activation.
Project older than April 2018 on XTM Cloud return error
To save disc space, XTM Cloud stores archived projects on a separate, secure server. This method of preservation was introduced in April 2018, and any project that was created before this implementation is only available for restoration by the XTM International Support team.
Solution: If your project matches those criteria, create a suitable ticket for the XTM International Support team and provide the following details:
Due to the nature of the method described above, the specified projects will be available after 6 to 12 hours.
A subcontracted project cannot be activated by an LSP
Solution: If you have received a project from a contractor, and it has been archived for whatever reason, contact your contractor and ask them to activate the project. If they activated it but the project is still inactive on your side, create a suitable ticket for the XTM International Support team and provide all the necessary details (as specified in the previous case).
A project cannot be activated after a migration or XTM Cloud upgrade
A project cannot be activated after a migration or XTM Cloud upgrade</h3><p>While our standard tests usually eliminate such issues, you can sometimes encounter this problem after your standalone server has either migrated or been upgraded.
Solution: If this is the case, create a suitable ticket for the XTM International Support team and provide all the necessary details.