Select to view content in your preferred language

Webhooks in ArcGIS Portal triggering a flow in Microsoft Power Automate - New URL length

397
4
2 weeks ago
Labels (1)
ColForbin
Frequent Contributor

I have a webhook in ArcGIS Enterprise 11.2 that triggers a MS power automate (MSPA) flow to run when a new item is created in Portal. I recently received an email from MSPA stating:

Your flow has a new trigger URL
The flow '<my flow name>' uses the request trigger, and its URL was recently changed. Any tools that  reference the old URL will break starting November 30, 2025.
Flow name: <my flow name>

The email provides this documentation: https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-run-issues/trigger...

When I try to update the URL for the webhook in ArcGIS Portal, I receive this error:
Database error occurred while processing webhook with name or id '<webhook id>' due to 'Unable to update webhook info for webhook with id : '<webhook id>' .'

When I attempt to update the webhook, ArcGIS Portal seems to be sending a "test request" to the URL.  I can confirm this in MSPA and see that the flow runs successfully. But the webhook does not get updated with the new URL.

I have tried creating a new webhook using the new URL from MSPA, and receive this error:
Database error occurred while processing webhook with name or id 'Test' due to 'Unable to add webhook registry named 'Test' for account 'Test'.'

I have noticed that the new MSPA request URL is 290 characters, whereas the old one was 229 characters.  I thought maybe there is a limit in ArcGIS Enterprise for the length of the webhook URL.  I tested this by creating a temporary request URL in webhook.site that is much shorter, and the webhook can be successfully created using this shorter URL (under 255 characters).

Is there a limit on the length of the URL for a webhook in ArcGIS Enterprise?  

 

4 Replies
MikeSchonlau
Frequent Contributor

We have the same question

ColForbin
Frequent Contributor

I have engaged with tech support on this and will convey the resolution here when available.

0 Kudos
MikeSchonlau
Frequent Contributor

I appreciate it

0 Kudos
StefanUseldinger
Frequent Contributor

Same problem here with ArcGIS Enterprise 11.5

0 Kudos