> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/extras/automations/environment-and-release-strategy.md).

# Environment and release strategy

This document outlines the operational details of Automations focusing on their execution in various environments and the strategies involved in their release.

<figure><img src="https://837703843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUX6zPRMFFK0yrTghj7cY%2Fuploads%2FIlrJUuCwvIJBoUvVoNwa%2FCleanShot%202025-03-24%20at%2018.49.47%402x-min.png?alt=media&amp;token=6da82e94-b9eb-4a53-83f0-1ebcdc9dbe2e" alt=""><figcaption></figcaption></figure>

## Unreleased Automations

Automations that have not been released yet operate under specific rules depending on the mode of execution.

<table><thead><tr><th width="150"></th><th width="163.4747314453125">CRON execution</th><th width="153">Webhook trigger</th><th>Execution in Automations Builder</th></tr></thead><tbody><tr><td><strong>Automation project version</strong></td><td>The <em>most recent version</em> </td><td><em>The latest</em> version</td><td><em>The latest</em> version</td></tr><tr><td><strong>Execution environment</strong></td><td>Data sources employed in these automations are executed using the <em>default DEV</em> environment</td><td>If triggered via a webhook without a specified environment, the <em>default DEV</em> environment is employed for data sources</td><td>The environment for data sources depends on the selected option in the environment selector. This selector is available only if there are data sources with pre-configured environments</td></tr></tbody></table>

## Released Automations

Once automations are released, it is safe to continue their development. The released version of the automation will remain in use for CRON and Webhooks ensuring stability in the production environment.\
This approach allows developers to enhance automations without interruptions or risks to the operational integrity of the current production version.

The following operational rules apply to *released Automations* depending on the mode of execution:point\_down:

<table><thead><tr><th width="145"></th><th width="170.13177490234375">CRON execution</th><th width="184">Webhook trigger</th><th>Execution in Automations Builder</th></tr></thead><tbody><tr><td><strong>Automation project version</strong></td><td><em>The latest PROD (production)</em> version</td><td>The <em>corresponding released version and data sources</em> of the specified environment (if includes an env specification)</td><td><em>The latest</em> version</td></tr><tr><td><strong>Execution environment</strong></td><td>If any data sources are connected, the <em>PROD</em> environment will be used for these data sources</td><td>The <em>Staging</em> environment is applicable and can be specifically used for webhook calls</td><td>The environment for data sources depends on the selected option in the environment selector. This selector is available only if there are data sources with pre-configured environments</td></tr></tbody></table>

{% hint style="warning" %}
The *Staging* environment is not available for CRON executions.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uibakery.io/extras/automations/environment-and-release-strategy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.