Hi Mohammed,
Sorry, I’m not sure if I am allowed to. But I did some checking on what might be the cause of the error, I found that the scope policies attached to the current API is causing the error. Does this mean that in the old fix that we have and the new Fix we implemented has a mismatch of PUT payload for the scope to update the API?
The only solution that I did was to delete all the scope policies that was implemented and recreate them, and the error was no longer there when saving the Changes in the API.
#webMethods#API-Gateway#API-Management