Quick answer: When two WireMock stubs both match the same request, the one with the lower priority number wins, and if priorities are equal the most recently added mapping wins. Relying on that implicit order makes a mock fragile. The reliable fix is to make the matchers specific so only one st...
Source: [Dev.to](https://dev.to/jeff_pdc/stub-priority-when-two-wiremock-mappings-match-the-same-request-4ik9)