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; } } }

Wanneer een record wordt aangemaakt in een feature layers stopt het triggeren

TimLohnes1

Dit is verschrikkelijk. Mijn flow stopte met triggeren wanneer nieuwe records worden aangemaakt. Dit is het begin van veel taken voor het personeel om te doen en bij te houden. Nu ligt het stil. Het draaide perfect gedurende 6 maanden. De verbinding is geldig.<\/P>

Ik kan data terugsturen en records in dezelfde laag zonder problemen bijwerken. Het triggert alleen niet bij het aanmaken van een record. Ik zag dat iemand maandag iets soortgelijks postte.<\/P>

ESRI, is er iets aan de hand waar we van moeten weten? <\/P>

Ik heb de flow opgeslagen, de trigger verwijderd, de trigger opnieuw toegevoegd - niets.<\/P>

Ik heb een nieuwe flow gemaakt met alleen die twee stappen en geen trigger.<\/P>

<\/span><\/P> <\/P> <\/P>

Vind meer berichten getagd met

Accepted answers

All comments

TimLohnes1

What version of Enterprise are you using?

11.2

Also, for layers to be used in PA, Editor tracking must be enabled.

It is now and always had been, but for reason when I first started working on the ticket with ESRI it was grayed out if I remember correctly.

Check with your IT if any firewalls or requests are being blocked. (it is unlikely if you had this working before). and nothing has changed)

Reaching out

I got lost a little bit lost on the rest. Made the webhook.site, created the new webhook, showed in webhook.site. Created new features and nothing happened.

Akshay Harshe

Tim, that is something to investigate then. What version of Enterprise are you using? Also, for layers to be used in PA, Editor tracking must be enabled. Check with your IT if any firewalls or requests are being blocked. (it is unlikely if you had this working before and nothing has changed)

There are a few steps to follow but this should help you in the long run to troubleshooting web hooks in general. To isolate the problem we can create a web hook outside of Power automate and ArcGIS. This will help us see if the webhook works. You can quickly create a webhook URL using this or similar sites https://webhook.site/ . This is a great tool to test webhooks and some other things in general. All you need is

Create a webhook URL here in webhook.site and copy it.
Navigate to :/server/admin/services/hosted/<layer>/webhooks/create
Use the copied url as a "hook url"
Changes to listen to could be `FeaturesCreated` or `*` to listen to all changes.
Make sure to choose webhook is set to `Active`

Once the webhook is created you should see the response on webhook.site

Do updates/ create features (depending on what changes you are listening to) in your layer to see the updates in webhook.site feed

This feed should return the "ChangesURL". This can be opened by first decoding then adding token at the end "&token=<token>". Token can be generated at the generatetoken endpoint or can be intercepted from one of the requests sent from portal using dev tools. Once opened you should see the status URL at the bottom of the page which you can click to if the job is completed. If the job is completed then the status URL should show link to "json" file which can be downloaded and checked for the relevant record you updated.

On a side note, we acknowledge that improving our documentation is necessary. Some of the doc on the MS site will be updated in the next release while we are Rehauling ArcGIS for O365 Esri doc. I am planning to have a robust doc for all Power Automate actions by end of the year.

TimLohnes1

Aksay,

I don't believe it is referenced from an enterprise gdb, just hosted. Not a Map Image layer.

Thanks,

Tim

Akshay Harshe

@TimLohnes1 are you using a Feature layer with data referenced from an enterprise geodatabase? or do you have a webhook on a Map image layer? If so, it is not working at the moment. This will be fixed in our next release.

Please confirm. If that is not the case, and the layer is a hosted feature layer then lets work on trying to isolate this problem.

TimLohnes1

Thanks. I don't see anything when I check Notification Status. Connections tab is fine,
I may have toggled some editing settings. Been through so many things. Also added lots of fields. That being said, this trigger doesn't work on any of our hosted layers. This trigger is not working at all. It used to work perfect.
I tried making a new app in portal and a new Connection in PA, but couldn't get that work either. I remember having a very hard time originally last year with that. But eventually got it to work. The documentation doesn't entirely match what I see.
Have worked with two ESRI members on a ticket and haven't gotten any clues yet.
I'm at the point where I am going to throw away a whole workflow process that several of our staff and vendors use.

Akshay Harshe

@TimLohnes1 I sorry, it is /server/admin/services/webhooks. Access the webhook correct webhook related to your service and check the `Notification Status` or status in the bottom for any errors.

I would also ask you to check `Connections` tab in Power automate home page to see if your connection has expired and needs re authenticate.

Also, did anything recently changed for this layer? e.g. Ownership/ editing capabilities or was the layer overwritten by some data. Any additional info will help for me to try and reproduce this issue.

TimLohnes1

Our administrator found services/webhooks url. It shows the layer/service name, folder, type, webhook name, webhook ID, Active. There are a lot for this layer half Active = True, half False. What do I need to investigate. I click on the webhook ID. But I have no idea how to troubleshoot this. I do have a ticket in, should I just go meet with them?

Akshay Harshe

Hi @TimLohnes1,

There hasn't been any changes or updates to ArcGIS Connectors for Power Automate in the last week. I am assuming you are using ArcGIS Enterprise connector. Can you check if the webhook is active at the /server/admin/webhooks/

TimLohnes1

A week later, trigger still not reacting to new features added.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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