> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/guides/integration-management/how-to-downgrade-a-task-to-an-older-version.md).

# How to downgrade a Task to an older version

This requires deletion of current version, but does not affect running Processes.

A Task in Frends is delivered as a versioned NuGet package, and a Frends Tenant keeps only one version of a given Task in use at a time. Because of this, there is no single "downgrade" button in the user interface. Returning to an older version means removing the version currently in use and then bringing the older one back.

This situation comes up most often when a Task update introduces a regression or a breaking change that affects a Process running in production. Restoring the previously working Task version lets you keep the integration running while the issue is investigated.

## Requirements

To downgrade a Task you need administrative access to Task management in your Tenant, since Tasks are managed from the **Administration > Tasks** menu. You also need access to the older version of the Task, either through the NuGet sources configured for your Tenant or as a NuGet package file that you can import manually.

Before you start, identify the exact version you want to return to. Task versions follow the `MAJOR.MINOR.PATCH` convention, where a change in the first number indicates a breaking change. Knowing the last known working version, for example `1.11.0` when `1.12.0` introduced the problem, helps you pick the right one.

## How Task versions behave in a Tenant

Understanding a couple of details makes the downgrade steps easier to follow. Only one version of a Task package can be in use in a Tenant at a time, so importing a different version effectively replaces the one currently in use.

Deleting a Task from the Task management view does not permanently remove it from the system. The package is only marked as deleted, which keeps older Process versions that reference it intact. When you later import the same older version again, Frends restores the package that is already stored rather than taking the contents of the file you select.

Frends also blocks importing a Task version that has already been imported. This means that to bring a specific version back into use, you first need to remove the version currently in the Tenant.

## Downgrading the Task

The downgrade is done in two parts: removing the current version and importing the older one. The steps below follow that order.

### Removing the current Task version

Open **Administration > Tasks** and locate the Task you want to downgrade. The list shows the version currently in use, so confirm that it is the newer version you want to move away from. Use the delete action next to the Task to remove it from the Tenant.

<figure><img src="https://4223974572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0p415NUmUmiF4ayjI81L%2Fuploads%2FwVBXDdV1CG9muKqCppG5%2Fimage.png?alt=media&amp;token=62b4dc5b-f04e-49e5-b660-fb6795b2db46" alt=""><figcaption><p>Delete option in Task management view. Task version is listed next to its name.</p></figcaption></figure>

### Importing the older version

Once the current version has been removed, bring the older version back into use. Use the **Search for Task** button to find the Task in the configured NuGet sources. The search view shows the available versions and lets you choose which one to import. Select the older version and import it.

<figure><img src="https://4223974572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0p415NUmUmiF4ayjI81L%2Fuploads%2F6OvWOcZM0JRpZDhcnNoM%2Fimage.png?alt=media&amp;token=31ed6b28-96ff-4b29-a44f-4051b19e0cf4" alt=""><figcaption><p>Selecting older version to import from a Task.</p></figcaption></figure>

If the Task is a custom one that is not available in any NuGet source, use the **Import Task NuGet** button instead and select the older NuGet package file from your computer.

<figure><img src="https://4223974572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0p415NUmUmiF4ayjI81L%2Fuploads%2FbW10sAotArc4QDVCGX41%2Fimage.png?alt=media&amp;token=22fcbe9f-ac32-42f7-9598-ac6972510987" alt=""><figcaption><p>Importing a Task from a file.</p></figcaption></figure>

## What happens to Processes using the Task

Downgrading a Task affects the Processes that reference it. When a Process uses a Task version that is no longer available, the Task shapes in the Process Editor become placeholders and their parameters may appear to be cleared. This is expected, because the Process was built against a version that is no longer present.

In many cases the parameters can be recovered. Opening the Process and selecting the matching Task type for each placeholder shape restores the parameter values that were configured earlier. After the shapes are back in place, save a new version of the Process so the changes are recorded.

Because a downgrade can touch several Processes, it is worth checking which Processes use the Task before you begin. The Task management view shows the usage of each Task, which helps you estimate the work involved.

## Downgrading in a version-controlled workflow

If your Processes are managed through import and export between environments, keep in mind that importing a Process that references an older Task version requires that exact version to be present in the target Tenant. If a newer version is already installed, the import can fail until the older version has been restored following the steps above.


---

# 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.frends.com/guides/integration-management/how-to-downgrade-a-task-to-an-older-version.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.
