---
schema_version: "1"
id: 7cdff411d5268c79277ec38337647fbc07e1c81e2e3ea524214e86023e26ba4c
title: Versioning Monitors
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-functional-monitoring/afm-version-monitors.md
canonical_url: https://docs.mulesoft.com/api-functional-monitoring/afm-version-monitors
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 465bba1f40473de1141debf91f85f3b3815b1021f9bdc8c4fbc51cfe8040e219
description: MuleSoft Documentation Site
latest: true
---
---
product: API Functional Monitoring
---

# Versioning Monitors

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Although you cannot directly version monitors, you can use schedule rules to specify versions. If
you were using an earlier version of API Functional Monitoring where tests were versioned, your test
version information is preserved, although it is displayed differently. Multiple test versions that
were migrated are now schedules of a single monitor.

To use the version information you had in the earlier version:

1.  Navigate to the old layout.

2.  Download a version of a test that should be preserved.

3.  Unzip the test package.

4.  Upload the unzipped directory.

5.  Choose a new test name.

6.  Specify a schedule rule that corresponds with the test version in the first step.

7.  Delete the version downloaded in the first step.
