Pipeline Blocked: Typo v13.0.0 succeeded, now cannot deploy lower version v1.4.0

(1) Share

Report

Posted on by wreta

Hi everyone,

I'm facing a versioning deadlock using Power Platform Pipelines with a Platform Host (not a manually created environment).

The issue:
By mistake, a solution was deployed with version 13.0.0 and it was marked as 'Succeeded' in the deployment history. Now, I need to deploy the correct version 1.4.0.0, but the pipeline blocks it with a version validation error because it is lower than the last successful record.

The Root Cause of the Conflict:
The version 13.0.0 was a typographical error; the intended version was 1.3.0.0. However, since the Pipeline successfully registered this 'typo' as a completed deployment, it has now set an impossibly high version ceiling. I am now trying to deploy the correct subsequent version, 1.4.0.0, but I am being blocked by the system's internal validation. I know the solution, move to 14.0.0.0 version, but I don't want to brake SemVer.

What I have tried so far:

Deleted the solution in the target environment (Production) to start fresh.
ried importing the fixed solution version (1.4.0.0) manually, but the Deployment history still shows 13.0.0 as the latest successful version.
Attempted to Redeploy an older successful version (v1.2.2.0) from the history to 'reset' the pointer, based on MS documentation.
Tried deploying directly from the Power Apps Solutions interface, but the validation error persists as it checks the Host's history.
Looked for the Deployment Stage Run tables to manually delete the v13 record, but since this is a Platform Host (PlatformEnv-europe), these system tables are not accessible/visible.

Environment Details (Redacted):

Host Environment Type: Platform-managed Host.
Source: Development Environment.
Target: Production Environment (currently empty of this solution).
Error: 'The version of the solution being deployed is lower than the version of the solution already in the target environment' (even though the target is empty, the Host history says otherwise).

Is there any way to reset or prune the deployment history for a specific solution in a Platform Host without having to increment the version to v14.0.0.0?

Any help from the community or MS staff would be greatly appreciated. Thanks!

deployments-histo...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building flows

Using flows

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 1,918 on at

Like (1)

Report
Copy link

Link copied!

In a Platform-managed Power Platform Pipeline, deployment history is immutable and used for version validation.

Once a higher version (like 13.0.0.0) is recorded as successful, you cannot deploy a lower version—even if the target environment is empty.

There is no supported way to reset or delete this history.

The only practical options are to increment the version beyond 13 (e.g., 14.0.0.0), create a new solution, or use a new pipeline/host.

Was this reply helpful? Yes No
Suggested answer

Valantis 4,793 on at

Like (1)

Report
Copy link

Link copied!

Hi @wreta

You've done thorough troubleshooting. Let me point to the confirmed path first.
Microsoft docs confirm there is a pipeline setting called "Allow redeployments of older versions" that must be enabled to deploy a lower version than the last successful deployment. Go to your pipeline settings and check if this is enabled. If it's not, enabling it should allow you to deploy v1.4.0.0 even though the history shows v13.0.0 as the last successful version.
Path: Open the pipeline configuration > select the pipeline > Settings > find the Allow redeployments of older versions toggle.
Ref: https://learn.microsoft.com/en-us/power-platform/alm/redeploy-past-solution-versions

If that setting is already enabled and the deployment still blocks, the next issue is that the Platform Host stores deployment history in Dataverse tables (specifically the deployment stage run records) that are not directly accessible in the UI for platform-managed hosts. Unlike custom hosts where you can open the Deployment Pipeline Configuration app and manage records directly, the platform host tables are managed by Microsoft.

At that point the only confirmed path is a Microsoft Support ticket. Provide: the solution unique name, the pipeline name, the environment IDs, and the erroneous v13.0.0 deployment record. Ask them specifically to delete or void the v13.0.0 deployment stage run record for that solution and pipeline combination. This is a data fix that only Microsoft can do on a platform-managed host.

There is no self-service workaround for resetting platform host deployment history that doesn't involve bumping the version.

Was this reply helpful? Yes No