Latest Contributions by KevinHibma

Thanks, Justin, we'll use your question as a motivator to get more information out. For your issue. A few things to try: You can setup a second webhook with the exact same parameters as your Notebook Webhook Receiver, just point it some place else, like https://webhook.site/  - This should give an idea if it's working Alternatively, ArcGIS Server debug logs should show if the webhook is being dispatched, or if there are errors Finally, if you set debug logs in the Notebook Server Administrator, you should see logging related to the notebook triggering. For the most part, setting up the receiver is the bulk of the work. The only thing you didn't note was the webhook secret key. Did you use the matching 32 character secret key while creating the webhook? This same value must be set when creating the webhook. ... View more

Is you ArcGIS Server using a proxy server to send requests? Can you try using a different webhook receiver? I like to suggest https://webhook.site - You can create a URL at this site and send webhook messages to it. It's perfect for testing. ... View more

@Hlynur - Perhaps you've already got an answer as it's been a few weeks. However, to explain: The video you link is for ArcGIS Online Hosted Feature Services. You're using Enterprise, or more specifically, referenced feature services, served from ArcGIS Server, which technically appear as an extension to the MapService as Jake mentions, when viewing them in the ArcGIS Server Administrator. This difference is significant. You won't find webhook administrative pages here in ArcGIS Enterprise (ArcGIS Server). You need to continue managing them from the original link you posted. To your problem of the webhook not sending a message. There are a few things you can do. First, if you enable debug logs in the Server, then perform an edit on the feature service, you should see debug logs about the webhook process. Look specifically for a messaging talking about webhook dispatched - If you see this message, you know the webhook message was sent and that would infer the problem is with the receiver. If you don't see this message, then there is a problem either with webhooks themselves, or possibly the FS isn't setup correctly to support edit and webhook workflows. ... View more

For organization webhooks (ie webhooks created in Portal), we have an issue logged and will attempt to fix it in the 12.1 release of Enterprise. The problem, as identified, the URL length has become longer than the database field allows for the URL value. It seems like Monitor has the same problem.   BUG-000179555 - When attempting to register an organization webhook in ArcGIS Enterprise using a Power Automate Request connector's "When an HTTP request is received" trigger URL, the operation fails with a database error. ... View more

Thank you for logging the suggestion - we've heard this request before, but getting it logged here where others can add their support is a great idea. We have not implemented this functionality as we do not have a database with ArcGIS Server to maintain these status messages (we handle the relatively small list of possible failed in another way). We do have some options, but they're complicated. We'll continue to evaluate this request, thank you. ... View more

As of the ArcGIS Enterprise 11.4 release, a new beta feature was added to Notebook Server: webhook receivers. This will come out of beta, and be a supported feature in ArcGIS Enterprise 11.5. IE. You can send feature service webhook messages to notebook server.   @JackFanZhang ArcGIS Online does not offer the same Notebook Server webhook receiver functionality as ArcGIS Enterprise. For ArcGIS Online Feature Service webhooks, you still need to send them to either a 3rd party receiver, or some sort of custom one you've built and deployed. ... View more

Unfortunately, we won't be able to handle this particular scenario with a webhook event. Internally, the user doesn't as much join the group, as they're simply allowed in based on the AD permissions. If we were able to support this, in theory we'd send a webhook event every time the user accessed the group (ie when the check is done). ... View more

Thanks for the poke on this @DougYurek  Back when I initially responded we began looking at it, but this was near the end of a release and it was much more complicated than we anticipated, and had to defer it. I have some time still in our current development cycle, so I'll get the team to take another look and see if we can make some progress on it.  ... View more

Check the Notification Status endpoint for the webhook. I suspect your webhooks are failing to send to your receiver and are being automatically disabled. If you check the settings in your root, you can see how many failures will trigger the disabling.       ... View more

Interesting idea. I understand the request from the webhook side, but I'm not sure a webhook is the best mechanism for this particular event. I'll bring it to the team and chat about it. The upcoming Enterprise 11.4 release will introduce audit logging in the portal. I realize you're looking for something beyond logs, but these audit logs will be very focused on security events and might provide the focused information you're after. ... View more

That's odd.  When you click create or edit, it's sending a HTTP message to that URL to check that 1) it responds and 2) its trusted (https /w valid security cert). If those checks fail, it wont allow you to create the webhook. 11.1 was our initial webhook release and we've fixed a few bugs since then. I'm not aware of any specific bugs in this area that might be causing this. I've created and seen others sending webhook payloads to GP Services; specifically async. ... View more

Yup, Async should get you past that. Postman will absolutely be doing the correct thing sending to your service. You can set the webhook to send as JSON, but I'm 99% sure that you can't "get" the value into the gp service as JSON via this trigger. It needs to come in as a form which would match a parameter on the GP Service. You can test sending your webhook payloads to https://webhook.site (free interest testing resource). This should give you an idea of how the payload as a form comes in. From there you might be able to determine how your code could handle that. ... View more

Hi @a-j-campbell  Two things happening here. When using a synchronous GP Service, this execution type will not return a response until the task finishes. So if the service takes 20 seconds to finish, it wont return a message to the webhook process saying "200-success" until then. The webhook send process looks for that 200-success message, but in this scenario it's most likely timing. It only waits for so long. I suspect that's why you're getting that error. Second, while you can send a message to a GP Service,  unfortunately in ArcGIS Enterprise 11.1 there is an issue when using url-form-encoded that the payload is not actually sending as a proper encoded form. This means that the GP Service is going to have problems ingesting the incoming payload. It's possible you might be able to work around it, but the payload doesn't get encoded properly. So it'll become tougher to handle that. ... View more

I don't think this will work. The sending webhook from Survey123 would need to send the webhook as a form-body.  Meaning, the incoming webhook body would look like: payload = { "eventType": "addData", "feature": { "attributes": {various attributes} } } Without the body parameter, the GP Service does not have a way to capture the payload and use it. ... View more

Hi Thomas, You won't see a "RabbitMQ" process by name. It's wrapped in another process. But I wouldn't go real deep looking here. You said you're using ArcGIS Enterprise 11.1? When you check your Server debug logs, do you see any errors related to webhooks? If not, thats good. If so, can you paste them here? If you're getting errors I'd suspect you would be seeing them quite often. If no errors, within the Server administrator, can you check /server/admin/system/webhookprocessors  (you'll need to type the webhookprocessors part in, it's not a published API). If you check the config, is it populated? If not, can you restart you ArcGIS Data Store, and then your ArcGIS Server, then Portal  (the restart is just to get everything into a state where that config would have information. Note - if it is already filled in, just try restarting ArcGIS Server. Further to your question, no, there is no configuration parameter you need to set or modify to enable webhooks. The config I mention above would automatically be filled in by the system: you cannot manually update it. ... View more