This topic lists questions or issues that you may encounter when working with webhooks and suggests possible solutions.
ArcGIS Enterprise is deployed in a disconnected environment behind my organization's firewall. Can I still configure webhooks?
Yes. To configure webhooks, you must use a payload URL that is reachable by your ArcGIS Enterprise portal. To do so, you can build a custom application and deploy it on your internal server.
If you subscribed to updates for your portal items, users, and groups, your webhook triggers whenever their properties have been updated. For example, if you have subscribed to updates for a specific item in your portal, your webhook triggers if an update was made to the item's title, tags, or thumbnail. A way to determine whether an action constitutes an update in your portal is to examine the network traffic. Any time an action results in the Update operation being called, that same action can also trigger a webhook that is listening for updates.
I am using Integrated Windows Authentication in my ArcGIS Enterprise portal. Can I still subscribe to users signing in and out of the portal (user/<username>/signIn)?
What happens if my payload URL goes down or becomes unavailable? Is there a way to recover a payload that was not delivered?
If a portal attempts to deliver a payload to an unreachable or nonresponsive payload URL or webhook receiver, the advanced parameters you have set will determine how and when the portal attempts another delivery. If these additional attempts also fail to deliver the payload, this counts as one failure toward the deactivationPolicy you set when creating the webhook. The webhook deactivates once this policy has been met.
You can go to the webhook's notification status to view all of the attempted payload deliveries and determine whether they were delivered successfully or not.