> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/pools/using-pools.md).

# Fetching and Using Environments

Once a pool is provisioned and has available instances, your team can start using them.

## Fetching an environment

<figure><img src="/files/gv4yACg1XPfK5ZtMQXp7" alt="Fetch Sandbox dialog"><figcaption><p>Fetch an environment from a pool — select the pool and set how long you need it</p></figcaption></figure>

Click **Fetch Sandbox** from the Pools page or from the DEV ENVIRONMENTS panel on the right. The dialog shows all pools with their current availability — how many environments are ready and the total capacity.

Select a pool and set the **Expiration Hours** — this is how long the environment will be assigned to you before it expires and returns to the pool. Click **Fetch Sandbox** to grab it.

Once fetched, you receive a password reset email from Salesforce to set up your credentials. The environment is immediately assigned to you.

You can see all environments assigned to you under **Dev > My Orgs > Assigned to Me** in the sidebar.

## Managing pool instances

<figure><img src="/files/1veg6Fapl3L7gjgTW9as" alt="Pool detail page"><figcaption><p>Pool detail view showing individual instances with status, assignment, and expiry countdown</p></figcaption></figure>

Click any pool name on the Pools page to see all its instances. Each instance shows:

* Its current status — **Available**, **Assigned**, **Provisioning**, or **Expired**
* Who it is assigned to (if anyone)
* When it expires, with a countdown (e.g., "2d left", "1h left")
* Action buttons to open, extend, or delete it

Switch to the **Pool Config (YAML)** tab to view or edit the pool's configuration.

## Where instances come from

<figure><img src="/files/bE4hdojeogNou2A9Ak7T" alt="Provisioned from card on the pool detail page"><figcaption><p>The Provisioned from card shows the base each instance is built on, its Salesforce id, and the owning org</p></figcaption></figure>

The pool detail page shows a **Provisioned from** card — the base each instance in the pool is built on. What it shows depends on the pool type:

| Pool type   | Provisioned from                             | Shown as                                                    |
| ----------- | -------------------------------------------- | ----------------------------------------------------------- |
| Sandbox     | A **source sandbox** it clones               | the sandbox name, its `SandboxInfo` id, and the owning org  |
| Sandbox     | **Production** (no source sandbox)           | `Production` and the license type                           |
| Scratch org | A **base snapshot**                          | the snapshot name, its `OrgSnapshot` id, and the owning org |
| Scratch org | A fresh **scratch definition** (no snapshot) | `Scratch definition` and the definition file path           |

The base is read-only here — a scratch org's snapshot lives in its scratch definition file in the repository, and a sandbox's source is set in the pool configuration. The Salesforce id is looked up live and shown alongside the name when the base exists; the name is shown on its own when it does not. To change the base, edit the pool's definition (see [Creating and configuring pools](/flxbl/codev/pools/creating-pools.md)).

## Extending an environment

<figure><img src="/files/bJcWE3xsFR3WRM781hf9" alt="Extend Sandbox Expiration dialog"><figcaption><p>Extend the expiration of an assigned environment by a specified number of days</p></figcaption></figure>

If you need more time with an assigned environment, click the extend action on the instance row. The dialog shows the current expiry date and lets you add days. The new expiry is previewed before you confirm.

This is useful when a feature takes longer than expected or when you need to keep an environment around for a demo or review.

## Returning an environment

When your lease expires, the environment is automatically returned to the pool and made available for others. You can also return it early from the pool detail page by unassigning it.

Returned environments may be refreshed, reused, or deleted depending on the pool's [expiration strategy](/flxbl/codev/pools/creating-pools.md#step-2-pool-config).

## Next

{% content-ref url="/pages/1fgX5e1zLiKl7hF33997" %}
[Pool Monitoring and Health](/flxbl/codev/pools/monitoring.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/codev/pools/using-pools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.