Solved! Go to Solution.
I've seen this error, most often when a new revision of the API you are working on is uploaded while tracing. In most cases, you can refresh the webpage and turn trace on again-- trace should function fine again.
If the problem persists, please contact our support team.
I assume this would be happening across all API proxies. Would restarting the message-processors and then redeploying the proxy help?
I have also seen this type of errors .See the link :https://community.apigee.com/questions/9667/comapi...
Looks like there is intermittent problem with free orgs due to network contigency as mentioned in the referred post.I hope trying after sometime ,the error vanishes.
I've seen this error, most often when a new revision of the API you are working on is uploaded while tracing. In most cases, you can refresh the webpage and turn trace on again-- trace should function fine again.
If the problem persists, please contact our support team.