Server side exceptions

Server apps can face issues when executing server side listener method (onStartAppMigration) and stop with an exception. We have seen cases where such server side failures caused the migrations of several apps to expire, as their cloud apps were not aware of server side failure and had not updated their transfer status to a settled state within 14-day time period.

How your cloud app can know about the occurrence of server side exceptions

Your cloud app will be notified with webhook event of type listener-errored (Connect) or a Forge event of type avi:ecosystem.migration:errored:listener (Forge) when the execution of your server side listener method onStartAppMigration has stopped with an exception. For Forge migrations, the event will also include details such as the type of exception and stack trace to facilitate easier debugging.

What your cloud app can do on the occurrence of server side exceptions (Connect only)

• Your cloud app can know more about the exception thrown by your server app using the fetch server side error API
• If your server app stops performing any migration operations for a given transfer on termination of onStartAppMigration, we recommend your cloud app to update the transfer status to a meaningful settled status based on data received so far from your server app.