We are currently encountering problems with Validate against Swagger assertion.
When this assertion is used within Policy Fragment that is then used in more than 1 policy that uses different swagger file,
It often gives faulty validation messages when both policies are called at the same time.
The validate swagger assertion is caching the swagger document which can cause problems when the assertion is used in a shared fragment where the document is changing with each call.
Release : 9.4
Component : API GATEWAY
Engineering is aware and is planning to improve the cache handling in a future release, for now we advise not to the the validate swagger assertion in a shared fragment