Error Deploying revision 3 to dev when revision 1 same proxy never deployed-

[abiramradhakris]

Getting following error

****************

Path /v1/Some/path conflicts with existing deployment path for revision 1 of the APIProxy Hello in organization cloud-apigee-organization, environment dev

*******************

Using Apigee Cloud, where I see that revision 1 was never deployed but revision 3 of same Proxy does not deploy indicating that revision 1 of same proxy name had same Path

[dchiesa1 · Accepted solution]

That error indicates that you have a path conflict between two proxies. You are trying to deploy a proxy to a basepath, and there is a different proxy, or a different revision of the same proxy, already listening on the basepath.

Keep in mind: the conflicting API proxy may not necessarily be a different revision of the API Proxy you are trying to deploy. The basepath of an API Proxy can be anything. If two proxies have the same basepath, they will conflict. Only one can be deployed, and the revision numbers of the respective proxies are irrelevant. They're just handy ways to identify the version of the configuration you're managing.