/
Project activation – most common issues & troubleshooting

Project activation – most common issues & troubleshooting

Introduction

By default, XTM Cloud projects go into an archived state 15 days after any non activity is detected, or 5 days for the finished projects, for the XTM memory preservation reasons.

Under certain restrictions, it is possible to extend the default period for auto-archiving XTM Cloud projects. For more information, do not hesitate to contact the XTM Support team.

Projects can be manually reactivated by you up to one year from the moment they are archived in the XTM Cloud UI. If this period is exceeded, the archived project is moved to an external server, and its restoration must usually be carried out by the XTM International Support team.

However, since XTM Cloud 13.10, activating archived projects stored on S3 and glacier can be performed via the XTM Cloud UI / API. You can seamlessly use the Activate option from the project’s context menu in the XTM Cloud UI [Projects → Project list → (enter a project’s context menu) → Actions → Activate project].

2025-01-28 08_31_10-Window.png

If the message: The activation process has started. This may take a while. pops up, it means that the project was archived a long time ago (more than 2 years), it is in deep archive storage, thus requiring 6+ hours to activate. Then, after that time, the project should activate automatically.

This article presents 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. 

IMPORTANT! 

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.

EXAMPLE:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pm="http://pm.v2.webservice.projectmanagergui.xmlintl.com/">

   <soapenv:Header/>

   <soapenv:Body>

      <pm:updateProjectActivity>

         <loginAPI>

            <client>XYZ</client>

            <password>Password123</password>

            <userId>20</userId>

         </loginAPI>