No Microsoft Power Automate GCC, tenho tentado configurar um webhook de serviço para enviar uma mensagem de e-mail "Quando um registro é atualizado em uma camada de feição", mas a URL de alterações "Buscar atualizações, mudanças ou exclusões da camada de feição" está sempre em branco. * Manter o controle das alterações nos dados (adicionar, atualizar, excluir feições) está habilitado * O webhook aparece no ArcGIS Server Admin na página de webhooks do serviço * O webhook aparece no ArcGIS Portal na página Configurações->Webhooks * O webhook está listado como ativo * O serviço é uma visualização de camada de feição hospedada, mas tentei configurar isso na camada de feição hospedada principal * Tentei usar as credenciais da conta do proprietário do serviço e da conta do administrador principal do site para configurar o conector ArcGIS Enterprise no Power Automate * Excluí e recriei o conector ArcGIS Enterprise no Power Automate * Tentei "Quando um registro é criado em uma camada de feição", mas o resultado é o mesmo * A página de Status de Notificação do webhook do serviço está sempre vazia * Não estou vendo nada nos logs do ArcGIS Server ou ArcGIS Portal quando tento acionar o webhook Estou sem ideias neste ponto. Gostaria de saber se perdi algo ou se isso é um bug no conector. Observarei que o webhook está usando logic.azure.us e pensei que a Microsoft descontinuou essa URL no final de novembro.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

O payload do webhook do serviço ArcGIS Enterprise 11.5 está vazio

joyoung_kerrvilletx

No Microsoft Power Automate GCC, tenho tentado configurar um webhook de serviço para enviar uma mensagem de e-mail "Quando um registro é atualizado em uma camada de feição", mas a URL de alterações "Buscar atualizações, mudanças ou exclusões da camada de feição" está sempre em branco. <\/P>

Manter o controle das alterações nos dados (adicionar, atualizar, excluir feições) está habilitado<\/LI>
O webhook aparece no ArcGIS Server Admin na página de webhooks do serviço<\/LI>
O webhook aparece no ArcGIS Portal na página Configurações->Webhooks<\/LI>
O webhook está listado como ativo<\/LI>
O serviço é uma visualização de camada de feição hospedada, mas tentei configurar isso na camada de feição hospedada principal<\/LI>
Tentei usar as credenciais da conta do proprietário do serviço e da conta do administrador principal do site para configurar o conector ArcGIS Enterprise no Power Automate<\/LI>
Excluí e recriei o conector ArcGIS Enterprise no Power Automate<\/LI>
Tentei "Quando um registro é criado em uma camada de feição", mas o resultado é o mesmo<\/LI>
A página de Status de Notificação do webhook do serviço está sempre vazia<\/LI>
Não estou vendo nada nos logs do ArcGIS Server ou ArcGIS Portal quando tento acionar o webhook<\/LI><\/UL>
Estou sem ideias neste ponto. Gostaria de saber se perdi algo ou se isso é um bug no conector. Observarei que o webhook está usando logic.azure.us e pensei que a Microsoft descontinuou essa URL no final de novembro.<\/P>
<\/P>

Encontre mais publicações marcadas com

Accepted answers

joyoung_kerrvilletx

@AkshayHarshe I just wanted to let you know that I found the problem. I migrated our ArcGIS Enterprise deployment to new machines back in March 2025 using the Join Site operation method. That process should have renamed all the machine names in config files to the new machine names. However, it did not change the machine name in a queue-store.json file on the new ArcGIS Server machine. I updated the file, restarted the ArcGIS Server service and now our webhooks are triggering.

All comments

Akshay Harshe

Hi @Joshua-Young,

Looks like you are successfully able to create a webhook and get a run under the flow. If you see a run with no errors inside it should work. On The ArcGIS Enterprise connector the second feature update after the webhook is created (3rd run on the flow) should include changes. When the flow is saved for the first time it should generate a successful run. The response should have message that the webhook on the server is created successfully. the first feature update will get the serverGens and the response should be empty and the third run should have changes.

Let me know if that helps. If you don't see the changes URL at all then I would need to know. Probably share some screenshots. If you see the logic.azure.com URL that we get from Microsoft and I don't think it should be an issue they are probably still rolling out that change.

joyoung_kerrvilletx

This is what I am seeing in Power Automate when I try testing the flow. I have changed current flow to trigger on updates instead of creation just to test what is wrong.

Nothing runs after the fetch step. I have tried the workflow described here https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/automate-field-notifications-with-microsoft-power-automate and another here https://support.esri.com/en-us/knowledge-base/how-to-generate-automated-email-notifications-for-arcgi-000030586

The flow is active on ArcGIS Enterprise

I have also setup a similar flow on another hosted feature service. It has successfully emailed once, but the changesUrl was also blank. The difference is I am not looping through the items to send the email. However even with this flow, I have tried to trigger it many times, and I have only received one email.

I checked the service webhook endpoint and the ServerGen field is blank on all of the webhooks I have made. Should that be the case?

The notificationStatus page is also blank for all of the webhooks.

Akshay Harshe

@Joshua-Young If you change your trigger from Features Created to Features updated and save it then it will delete the old webhook and create a new one and you will run into following again:

Once the new webhook is created you will see a run with a message that `The webhook was successfully created on the feature layer`. If you make a change to the feature layer to trigger your webhook the second run should return null response. All the changes you make to the feature layer after that should be received by the flow. This is expected behavior.

If you make several changes which triggered the flow a few times and you still don't see the changesURL populated then we might have an issue. Please let me know.

The changes URL needs to be sent back by the webhook for the flow to run. This could be also an issue on the server.

The serverGens value on the webhook endpoint does not show any thing.

Please see these additional tips for troubleshooting webhooks for your reference: Guide: Troubleshooting ArcGIS and ArcGIS Enterpris... - Esri Community

joyoung_kerrvilletx

@AkshayHarshe the changesUrl is always blank no matter what I do for any service or trigger event. I have been going over the logs and I find this error once an hour. I replaced the GUID that was in the error with <GUID> since I don't know if that is sensitive info or not.

Webhook log: Error in Webhook Processor. init WebhookProcessors failed. FS Webhook processor init failed Connecting to queue : <GUID>_FS_Raw_Events_Queue failed. Could not create a queue with id : [<GUID>_FS_Raw_Events_Queue] Connection refused: getsockopt.

I have opened a support ticket. The odd thing is I first tested a service webhook back in April when we were on ArcGIS Enterprise 11.4 and I had no issues. The webhook triggered every single time. Now that we are on 11.5 I cannot get a service webhook to do anything.

joyoung_kerrvilletx

Akshay Harshe

@Joshua-Young Thanks for updating! 🙂

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.