Fired event itemupdating which wasn t handled Videosxxxwebcam
This last task triggers the App Uninstalling event.
The App Uninstalling event is synchronous and you can use it to cancel the uninstallation, which would leave the add-in in the second stage recycle bin.
Each time it calls the handler, your code starts again from the beginning.
But you generally don't want your handler to redo things it has already done, such as create a list on the host web, and you can't know if your rollback logic was completed, or even triggered, before the handler timed out.
If it is restored from there and used again, it may fail to work without that database entry.
First, a user must remove the add-in from the recycle bin, which moves it to the second stage recycle bin.
Second, a user must remove the add-in from the second stage recycle bin.
For more information, see Include rollback logic and "already done" logic in your add-in event handlers. NOTE] When you install an add-in with Tenant scope, it is installed to the add-in catalog site collection, and the App Installed event runs then and only then.
The add-in is visible in multiple websites in the tenancy, but the event does not run separately for each of these. After four timeouts, Share Point rolls back the entire add-in installation.
Add-in events are also handled by remote web services, but they are configured differently in the add-in package from list and list item RERs, so they are treated as a separate category of component.