Early Access Releases – FAQ

Contents

• What are Early Access releases?
• Why does Leapwork release Early Access builds?
• How do I access Early Access builds?
• Can I upgrade from a GA release to an Early Access release?
• Can I downgrade from an Early Access release to a GA release?
• What's the upgrade path for EA version 2025.1.235?
• Are EA builds supported?
• How are bugs and incidents handled in EA builds?
• How can I provide feedback?
• What precautions should I take before using an EA build in a test environment?
• When will EA features be released to GA?
• Will there be a unified upgrade path between GA and EA in the future?
• Why are there separate GA and EA release tracks?

What are Early Access releases?

As of March 2025, Leapwork provides Early Access (EA) builds, full product versions released ahead of the regular release cycle. These builds are available in the Downloads section of the Customer Portal and are clearly marked as Early Access.

These builds let you explore upcoming features before general availability and share feedback with our product team. While they offer early insights, they are experimental and not intended for production use. 

Note: EA builds may have limited functionality and are not covered by our standard support agreement.

Why does Leapwork release Early Access builds?

We follow five core principles, foremost among them is putting customers first. Early Access allows us to:

• Gather feedback from early adopters

• Validate new features

• Let you influence the direction of Leapwork.

If you're passionate about shaping the future of test automation, EA builds are your chance to contribute.

How do I access Early Access builds?

You can download the latest EA builds from the Downloads section of the Customer Portal. We recommend installing them on a separate test machine, not in your primary Leapwork environment.

Can I upgrade from a General Availability (GA) release to an Early Access release?

No. GA and Early Access are separate release tracks with different compatibility and support considerations. To evaluate an EA release, install it in a non-production test environment.

Can I downgrade from an Early Access release to a GA release?

No. Direct downgrades are not supported. To return to a GA version, uninstall the EA version and install the GA version in a clean environment. Always back up your test data before installing preview builds.

What's the upgrade path for EA version 2025.1.235?

To upgrade to EA 2025.1.235, start from version 2024.2.32. Do not upgrade via version 2025.1.173, as this may cause issues.

Are EA builds supported?

Limited support is available for installation and feedback-related questions. However, EA builds are not covered by production SLAs. See our support policy for details:
Leapwork Support Policy

How are bugs and incidents handled in EA builds?

We track and review all reported issues. However, bug fixes in EA builds are not prioritised over fixes for GA releases.

How can I provide feedback?

Use the built-in feedback channels in the product or reach out via the Leapwork Customer Portal.

What precautions should I take before using an EA build in a test environment?

• Back up all flows and test data.

• Install on a separate machine from your production setup.

• Review the known limitations of the EA build.

When will EA features be released to GA?

After successful validation and review, selected EA features will be included in a future GA release. Updates will be shared via our Product Roadmap.

Will there be a unified upgrade path between GA and EA in the future?

We are exploring options such as feature toggles and trial modes. However, due to the on-premises nature of our platform, implementing a unified upgrade path remains complex.

Why are there separate GA and EA release tracks?

On-premises software environments don’t always support feature toggles or staged rollouts. Maintaining a separate EA release line allows us to safely test features like the new Recorder with select users before general release.