﻿# Troubleshooting

> Known issues and limitations for project templates

:::div{.warning}
Project templates are in Public Preview. The feature is still evolving and standard SLAs don't apply. We don't recommend it for production workloads yet. It's available to Enterprise customers on Cloud and to self-hosted customers running Octopus 2026.2+. We'd love your feedback as we work towards General Availability.
:::

## Public Preview limitations

Project templates are in Public Preview. The following features are not yet supported and are planned for future releases:

- Ephemeral environments, including ephemeral environment channels
- Retention policies on templated project releases (you can configure them, but they have no effect)
- Cloud target discovery on steps (see below)
- Cloning a project template through the Octopus UI
- Creating and managing project templates through the REST API, CLI, or Terraform provider
- Runbooks
- Import and export of templated projects
- Inline variable configuration within the deployment process editor
- Scoping Insights reports to channels in a templated project (you can still scope a report to the templated project itself)
- Templated projects in compliance reports

We'll update this page as the feature evolves.

:::div{.info}

Support for configuring Platform Hub External Feeds is available from Octopus 2026.4.1770

Support for configuring project triggers and runbook scheduled triggers for templated projects on the consumer side is available from Octopus 2026.4.1770

:::

## Deployment freezes

The environment filter on deployment freezes doesn't list templated projects.

## Projects dashboard

The dashboard doesn't display deployments for templated projects.

## Cloud target discovery

Project templates can't supply the account that cloud target discovery uses on a step. To use cloud target discovery in a templated project, configure it on the templated project itself. See [cloud target discovery](/docs/infrastructure/deployment-targets/cloud-target-discovery) for more information.

## Cloning project templates

You can't clone a project template through the Octopus UI. To clone a template:

1. Copy the template's folder in the Platform Hub Git repository.
2. Rename the folder to the desired slug.
3. Update the template name inside `template.ocl`.
4. Commit and push the changes.
5. Refresh the project template list in the Octopus UI to find the newly created template.
6. Publish the template and configure the spaces that have access to it.

## Public API

The Public Preview release doesn't support creating and managing project templates through the REST API. We're planning REST API support for a future release.

## Losing access to an Octopus Enterprise license

Project templates and all Platform Hub features require an Enterprise license. When you no longer have an Enterprise license, project templates behave differently.

### What will continue to work

- Existing deployments can be redeployed.
- Auto-scheduled deployments will continue to run.

### What will no longer work

- Users will lose access to Platform Hub, including the ability to create and manage project templates.
- You can no longer update or publish project templates.
- You can no longer create new projects from project templates.
