This page applies to Apigee and Apigee hybrid.
View
Apigee Edge documentation.
This section shows some common deployment flows and the various stages of those flows. For information on how and where to see the deployment status usig the Apigee UI and API, see Viewing deployment status.
Proxy revision deployment flow
The following table describes the flow when you deploy an API proxy revision:
| Step | Action | Description |
|---|---|---|
| 1. | Proxy revision 4 is deployed, and you edit proxy revision 5. | Revision 5 is not deployed. |
| 2. | You click "Deploy" for revision 5. | The API proxy is not deployed. |
| 3. | You wait approximately 10 seconds. | Deployment in progress. 50% (for example) complete. |
| 4. | You wait for approximately 20 seconds. | Deployment of the API proxy revision is complete. You can test your API. |
Error flow
The following table describes the flow for deployment errors:
| Step | Action | Description |
|---|---|---|
| 1. | Proxy revision 4 is deployed, and you edit proxy revision 5. | Revision 5 is not deployed. |
| 2. | You click "Deploy" for revision 5. | The API proxy is not deployed. |
| 3. | You wait approximately 10 seconds. | Deployment in progress. 50% (for example) complete, but there is an error deploying due to base path conflicts. |
| 4. | You wait for approximately 20 seconds. | There's a problem that needs to be resolved.
The detail view shows that there was an error during deployment that needs to be resolved. |