URL Matching Failure After Merging REST Transactions into Existing VSI

Products

• Service Virtualization

Issue/Introduction

 When merging new REST transactions into an existing Service Image, all previously functional path-parameterized transactions stop matching. While the transaction data merges correctly, the global URL-matching configuration (specifically the REST Data Protocol Handler rules on the VSM's Listen Step) becomes corrupted or decoupled during the merge process.

Symptoms:

• Newly recorded and merged transactions appear correct in the VSI.
• Existing path-parameterized transactions, which functioned perfectly before the merge, return "Operation match failure" or "No Stateless Match" errors post-merge.
• This behavior persists whether using the merge tool or re-recording to an existing image.
• Recapping from a fresh recording fixes the matching, confirming the issue is specifically triggered by the "merge into" workflow.

Environment

All supported DevTest releases.

Cause

When you record a brand-new transaction separately and then merge it into your existing consolidated image, DevTest merges the transaction data itself, but it does not reliably reconcile the Listen Step's filter configuration between the two. If that merge overwrites, duplicates, or drops the Base Path/path-param filter on the original VSM's Listen Step, the effect isn't limited to the new transaction — it breaks URL matching for every transaction in the image, because that filter governs how incoming requests get parsed before matching against anything. That's exactly your symptom: one merge, and all previously-working path-param transactions stop matching.

Resolution

1. Open the VSM associated with the VSI.
2. Navigate to the Listen Step.
3. Inspect the REST Data Protocol Handler (DPH) configuration.
4. Manually verify and re-apply the Base Path and path-parameterization filter rules to ensure they align with the newly merged transaction structure.