> ## Documentation Index
> Fetch the complete documentation index at: https://namespace.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting cache volumes

Debugging issues that involve cached data is difficult because the workflow environment can change between runs.
To inspect a cache volume directly, you can attach it to a one-off instance.

## Connecting to cache volumes

Namespace allows you to create one-off instances and connect them to a cache volume.

<Steps titleSize="h3">
  <Step title="Create an instance">
    Using [nsc create --volume](/docs/reference/cli/create#--volume), you can create an instance and attach a cache volume.

    ```bash theme={null}
    nsc create --volume cache:<cache-tag>:/cache:<size>gb
    ```

    The size and the tag should match what you see on [the dashboard](https://cloud.namespace.so/workspace/storage).

    **Note**: this follows standard [cache volume semantics](/docs/architecture/storage/cache-volumes#cache-hits-and-misses). Namespace tries hard to provide you with the latest cache version, but you may rarely see a slightly stale cache instead.
  </Step>

  <Step title="Connect via SSH">
    ```bash theme={null}
    nsc ssh <instance>
    ```

    Inside the instance, you can find the cache contents at the mount point:

    ```bash theme={null}
    ls -al /cache
    ```
  </Step>
</Steps>

## Setting breakpoints

When you want to investigate a particular cache state, you can temporarily add a [breakpoint](/docs/solutions/github-actions/debugging/interactive-access#setting-breakpoints) to your workflow definition and jump into an interactive SSH session.

```yaml {8-9,15-21} theme={null}
jobs:
  tests:
    runs-on: namespace-profile-with-caching

    steps:
      - uses: actions/checkout@v4

      - uses: namespacelabs/nscloud-cache-action@v1
        with: ...

      - name: Run tests
        shell: bash
        run: ...

      - name: Breakpoint if tests failed
        if: failure() # Remove this for an unconditional breakpoint
        uses: namespacelabs/breakpoint-action@v0
        with:
          duration: 15m
          authorized-users: <your-github-username>,<another-github-username>
```

For the full breakpoint mechanism, including `breakpoint-action`'s options, duration, and authorized-users, see [Debugging: Interactive access](/docs/solutions/github-actions/debugging/interactive-access#setting-breakpoints).

## Next steps

* [Interactive access](/docs/solutions/github-actions/debugging/interactive-access)
* [Cache Volumes overview](/docs/solutions/github-actions/caching)

## Hands-on support

Got stuck? Need help with debugging one of your workflows? Our team is here to assist:

* **Technical support**: Reach out to [support@namespace.so](mailto:support@namespace.so) to talk to one of our engineers.
* **Community**: Join our community [Discord](https://discord.gg/DqMzDFR6Hc) to learn about tips and best practices.