There are some situations that might prevent you from using LifeTime to deploy your applications from a source to a target environment (e.g., from Development to QA).
- LifeTime is incorrectly considering the dependencies are incompatible.
- LifeTime is not showing the version last published in the source environment.
- The deployment gets stuck in one of the steps.
- The synchronization of the source or target environment is stuck.
When you are not able to use LifeTime to deploy your applications, follow the validations below to troubleshoot a potential issue.
Check the network connectivity between environments (on-premises only)
If you have on-premises environments, make sure there is bidirectional communication between LifeTime and both source and target environments:
Check the status of OutSystems services
Check the status of the OutSystems services in both source and target environments to guarantee they are working correctly:
Go to the Service Center console of the source environment (
Go to Monitoring » Environment Health. A green checkmark means the service is working correctly.
Do the same for the target environment.
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:
Go to the Service Center console of your LifeTime environment (
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.
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 an environment, you can try to deploy the application through Service Center as a workaround.