Select to view content in your preferred language

UN and OnPost Event Webhooks - should this work?

1213
11
Jump to solution
05-07-2026 10:10 PM
geovolve
Occasional Contributor

@MikeMillerGIS @RobertKrisher and others, I'm hoping you can help out here...

We have an Electric UN running on v11.5 and would like to trigger an external activity that runs after the OnPost Webhook is triggered.

The webhook has been setup fine and the trigger works. The recipient (FME Flow) sees the notification that the event has been triggered and then makes the second request to the 'extractChanges' url. This never results in a valid response. We can see in the ArcGIS Server logs that a geoprocessing job has been created and the job file has been written to the output folder. However, it seems to fail at writing any information to the scratch.gdb in the jobs folder.

We've enabled verbose logging just to see if we can determine where it's failing without any luck. We've enabled all capabilities across the Feature Service and the Utility Network Service and have tried different version properties (public, protected, private), also without any luck. We've even tried looking at epoch date values and they all seem to align.

So, should this onPost webhook work for UN Services, and if so, are there any specific properties that need to be defined at the version, services or sde level?

Any tips or direction would be much appreciated!

Cheers,

0 Kudos
11 Replies
geovolve
Occasional Contributor

Thanks @GaryMacDougall  and @gis_KIWI4 - these are working well now.

Do you know if there is method for determining the name of the branch version that was used when the OnPost webhook was triggered? Is there potentially a separate request to versionManager, using servergen information to determine the version name?

0 Kudos
geovolve
Occasional Contributor

As an update, the last query has been answered in another post: https://community.esri.com/t5/arcgis-utility-network-questions/how-to-determine-version-name-from-on... 

In short, its a feature request