Loading

Custom Policy Implementation Updates Behave Differently for Patch vs Minor/Major Versions in API Manager

Fecha de publicación: Jun 29, 2026
Descripción

When managing custom policies in Anypoint API Manager, the implementation version update behaviour differs depending on the type of semantic version bump published to Exchange:

  • Patch version bump (e.g. 1.0.0 → 1.0.1): Policy definition version updates in API Manager, but the implementation does not update automatically. Manual action is required.
  • Minor version bump (e.g. 1.0.0 → 1.1.0): Implementation updates automatically.
  • Major version bump (e.g. 1.0.0 → 2.0.0): Implementation updates automatically.

Why Does This Happen?

This is working as designed. API Manager uses semantic versioning (semver) conventions to determine when to auto-update the implementation:

  • A patch version change (x.y.Z) signals a backward-compatible bug fix — the existing implementation is still valid and compatible. Auto-updating the implementation on every patch would trigger unexpected redeployments for customers who have not yet validated the new patch in  their environment.
  • A minor or major version change signals new functionality or a breaking change — API Manager treats these as meaningful enough to warrant an automatic implementation refresh.

Symptoms

After applying a new patch version of a custom policy to an instance in the API Manager:

  • API Manager shows the latest policy definition version as selected.
  • However, the Mule application logs show the policy running on the old implementation version.
  • No error is displayed — the policy continues to function using the previous implementation.

 

Solución

Option 1 — UI (immediate)

  1. In API Manager, navigate to the API instance where the policy is applied
  2. Click on the applied policy
  3. Click "Check for Implementation Updates"
  4. Confirm the update

The implementation will immediately update to the latest published patch version, and the new implementation version will be reflected in the Mule application logs.

 

Option 2 — REST API (for automation / CI/CD pipelines)

Send a PATCH request to the policy endpoint with the implementationAsset field:

PATCH /apimanager/api/v1/organizations/{orgId}/environments/{envId}/apis/{apiId}/policies/{policyId}

{
	"implementationAsset": {
		"groupId": "{your-group-id}",
		"assetId": "{your-policy-asset-id}",
		"version": "{new-patch-version}"
	}
}

 

Note: The version specified must be a published, runtime-compatible implementation. If not, the API returns: "The policy implementation from request body is not available for the API."

 

This API call can be incorporated into your CI/CD pipeline immediately after publishing the new patch version to Exchange — ensuring the implementation is always kept current without manual UI intervention.

Número del artículo de conocimiento

005387938

 
Cargando
Salesforce Help | Article