Application statuses in environments
What does this page cover?
Learn how environment statuses reflect the state of your application when adding or publishing it in environments. Before you proceed, ensure you have a clear understanding of environments and the process of adding and publishing applications within them.
1. Environment statuses
When adding or publishing applications in environments, you can track the progress through status messages specific to each state of the process. These statuses help you monitor deployments and quickly identify issues. They also ensure that your application and its dependencies are properly deployed across the environments.
Environment application statuses are grouped as:
- Common statuses
- Statuses when adding an application to the environments
- Statuses when publishing an application in the environments
1.1. Common statuses
These are common statuses that are independent of the statuses in the process of adding or publishing applications to the environments. They appear on the respective environment cards for the application, as shown below.
Development environment | |
Status | Description |
No changes available | The application has been successfully created in the development environment, and no modifications have been made after its creation, or all changes have already been published, and so there are no pending updates to publish. Only applications with changes can be published to the stage environment. Therefore, apps with this status cannot be published. |
Changes available | The application in the development environment has been modified. Only applications with this status are eligible for publishing to the stage environment. |
Locked | The application is being published to the stage environment and is locked from any modifications until the publish process is complete. Click here to learn more about the environment locking mechanism. |
| Stage environment | |
| Status | Description |
| Stage app not yet created | This status indicates that the application has been added to the environment without automatically creating it in the development and stage environments. When this happens, app creation must be manually initiated. |
| Not yet published | The application was added to the environment during its creation and hasn't been published to the stage environment. |
| Production environment | |
| Status | Description |
| Not yet published | The application has been added to the environment during its creation and hasn't been published to the production environment. |
1.2. Statuses when adding an application to the environment
When an application is added to environments, it is deployed to both the development and stage environments along with its dependent applications. The apps will remain inaccessible in these environments until the main application and all its dependent apps are successfully created. If an error occurs in any of the apps during creation, it must be resolved, and the affected app must be redeployed in the respective environment. Until this process is complete, all dependent apps in the development and stage environments will remain locked, while the production environment stays accessible.
You can track the deployment progress through the status displayed on the respective development and stage environment cards for the application.
Development | |
Status | Description |
Development app not yet created | This status indicates that the application has been added to the environment but has not yet been created in the development and stage environments. In such cases, you must manually initiate app creation in the development environment. |
Creating development app | The application is being created in the development environment and will be inaccessible during this process. |
Waiting for dependent apps | The app has been created and is now waiting for all its dependent apps to be created (or) The app is currently queued for creation in the development environment. |
Waiting for stage app creation | The app and its dependent apps (if any) have been created in the development environment, and it is now being created in the stage environment. |
Development App creation complete | The app has been successfully created in both the development and stage environments. The version number will be displayed in the stage environment to indicate the published version. |
Error in app creation - View Details | The app creation failed in the development environment. Refer to the details for resolution. |
Dependent apps failed - View Details | This status appears in all dependent apps when the app creation of any dependent app fails in either the development or stage environment. Refer to the details for identifying the specific application and environment where this issue occurred. The specific app where the failure occurred in the development environment will display the following status: 'Error in app creation – View Details'. |
Stage | |
Status | Description |
Stage app not yet created | The app has been added to the environment without being automatically created in the development and stage environments. In this case, app creation must be manually initiated, or the app creation has failed in the development environment and has not been initiated in the stage environment yet. |
Waiting for development app creation | The application is being created in the development environment. |
Creating stage app | The app has been created in the development environment and is now being created in the stage environment. |
Waiting for dependent apps | The app has been created and is now waiting for all its dependent apps to be created, or it is currently queued for creation in the stage environment. |
Stage app not yet created – Error in app creation | The app creation has been failed in the stage environment. Refer to the details for resolution. |
Dependent apps failed - Error in app creation | This status appears in all dependent apps when the app creation of any dependent app fails in either the development or stage environment. The specific app where the failure occurred in the stage environment will display the following status: 'Stage app not yet created – Error in app creation' |
1.3. Statuses when publishing an application in the environments
When an application is published to an environment, Zoho Creator initiates a structured process to apply the latest changes to the stage or production environment. You can monitor the progress and outcome of the publish process by hovering over the icon displayed next to the version in the respective environment, as shown in the image below.
These statuses help you understand whether the application is in queue, being published, completed, or if the process has been interrupted.
When an application is published to the stage environment, the development environment is locked to prevent any modifications during the publishing process. However, while publishing the application to the production environment, the development environment remains accessible. Click here to learn more about the environment locking mechanism.
The table below lists all statuses displayed during the application publishing process.
Status | Description |
V{0} is in publish queue |
|
V{0} is in progress (Maintenance Mode) |
|
V{0} is in migration process (Maintenance Mode / App Accessible) | Indicates that the app has been published and is undergoing data migration. During this stage, the existing data in the target environment is migrated to align with the new configuration like schema or configuration updates. The app may go through the following states during this process:
|
V{0} is published | The application has been successfully published to the target environment. |
Error in Publish | An error occurred during the publish process. Click the status to view detailed error information. |
Publish cancelled | This status appears when publishing multiple applications and an error occurs in one of the selected apps. As a result, the publish process for all other apps in the queue will be canceled before it begins. |
Publish aborted | This status appears when multiple applications are published simultaneously and an error occurs during the publish process of any one of the selected applications. As a result, the publish process for all other applications will be aborted. |
Publish changes reverted | This status appears when the publish process completes but encounters issues that trigger a rollback, restoring the environment to its previous stable state. For example, If version V2.0 is currently live in production, and version V3.0 is published from stage to production, but an error occurs after publishing, the system will automatically roll back the production app from V3.0 to V2.0. |
2. Related links
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Understand Environments
In a nutshell Environments in Zoho Creator provide a structured platform for developing, testing, and deploying changes to the live application efficiently. It serves as an SDLC framework within Creator, enabling phased software development by ...Track software development lifecycle
Requirement Use Blueprints feature to track and manage the process of software development. Use Case A software company uses blueprints to track and manage the software development lifecycle. Various blueprint actions are needed to mark the ...Adding applications to environment
What does this page cover? Learn to add applications in environments. Make sure you have a comprehensive understanding of environments before you continue. Availability Available only on Creator 6 version and all paid plans. Super admins and admins ...Managing stage environment
The following stage environment actions are available to users: Access Settings Logs The above options will be displayed when you click on the ellipsis for the required app listed in the Environments page. Access Opens the app live mode in Stage ...Remove applications from Environments
What does this page cover Learn how to remove applications from an environment. This disables the environment feature for those apps, but allows you to access them as non-environment apps. These standalone apps will be available under Solutions. ...
New to Zoho LandingPage?
Zoho LandingPage Resources