Skip to main content





LifeTime synchronization is stuck

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • Symptom

    Environment synchronization in LifeTime is taking longer than expected.


    When the synchronization of an environment in LifeTime is stuck, follow the validations below to troubleshoot a potential issue.

    Verify that you are running the latest version of LIfetime and Platform Server

    Keep LifeTime and Platform Server updated in order to take advantage of the latest improvements in synchronization procedures. See this article for more information about version compatibility.

    Check the connectivity between environments (self-managed only)

    If you have self-managed environments, make sure there is bidirectional communication between LifeTime and the synchronizing environment:

    1. Test the connectivity from LifeTime to the synchronizing environment.

    2. Test the connectivity from the synchronizing environment to LifeTime.

    Check the servers Timezone (self-managed only)

    If you have self-managed environments, make sure the database server and the application environment servers (controller and front-ends) are set with the same Timezone, as described in OutSystems Timezone considerations.

    Check the status of LifeTime Processes

    Environments synchronization in LifeTime is based on OutSystems Business Process Technology.

    Check the status of the Processes for potential issues:

    1. Go to the Service Center console of your LifeTime environment (https://<LifeTime_environment>/ServiceCenter).

    2. Go to Monitoring » Processes. You should have no Suspended Instances and no Active Instances with Errors. If you get any of these, open a support case to get help from OutSystems Support.

    LifeTime Process Monitor

    Still having problems?

    If the above validations did not help you to solve the issue and you need further assistance, open a support case to get help from OutSystems Support.

    If you have a critical need to deploy an application to that environment, you can try to deploy the application through Service Center as a workaround.

    If your infrastructure is self-managed (not required for OutSystems Cloud), make sure to attach the following information to your support case:

    • Was this article helpful?