Latest Contributions by AkshayHarshe

@TL2 are you using ArcGIS Online connector? The ArcGIS Connector creates a server side webhook on your feature service which you can see in the Feature Service -->Settings. Unfortunately, ArcGIS Connector for Power Automate doesn't have control over how and when the webhook will trigger. The flow will start running when ArcGIS ( enterprise) webhook triggers. So far standard time is approx 2-5 minutes. If you have large geometries like detailed polygons  being edited this may take a bit longer We have seen slow performance with ArcGIS Online webhooks in the past and appropriate people are involved. Can you let me know what your feature service URL starts with and what # it has in `services#.arcgis.com`? e.g. "services5.arcgis.com" or "services.arcgis.com" ... View more

@TylerGraham2 Can you try deleting and re adding this action? This was addressed in the 2026.1 release. You should now see a dropdown to narrow down the feature layer from your contents, organization etc. Let me know if this works.   ... View more

@LindseyDanforth_Boulder have you tried this: Quick Tip: Keeping the ArcGIS Connectors for Power Automate Refresh Token Valid? Let us know if this works for you. ... View more

@GBPTechForester  If you are referencing enterprise layer in Online and trying to access it with ArcGIS Connector it will not work. It shouldn't show the feature layer in the dropdown. User needs to be owner of the FL or an admin to create webhook. You must use ArcGIS Enterprise connector. That said, other actions may work such as  Get data from feature layer. When I try using enterprise connectors to access the layers directly on our local enterprise server, the layer becomes unresponsive for as long as there is a flow that is turned on and accessing that layer ... I have gotten this flow to trigger successfully, but after a few moments the layer crashes on all machines that can access it and I have to restart the server to make it accessible again. This is  very interesting and concerning if it is a bug. It is most likely related to the resources as you mentioned but mainly to do with Enterprise or feature service, as Power Automate connector will only route the request and responses. I won't rule it out but curious to know. Unfortunately, I can't see any screenshots maybe those will give me more information. If possible, I would try to reproduce this outside of Power Automate connectors using webhook.site or something similar to rule it out. see Guide: Troubleshooting ArcGIS and ArcGIS Enterpris... - Esri Community I will also recommend you to get in touch with technical support. ... View more

@Bud I hear your, getting IT to get you a license can be rough. POC and making a case is of course way to go. Trust me I know, when I joined this team I was asked to use the 90 day free trial until my licensing and approvals were sorted out. 😄  ... View more

@Bud what @CalvinHarmin said, you do need a power automate premium license for using ArcGIS, ArcGIS Enterprise and ArcGIS PaaS there is no additional licensing required from our end if you have appropriate ArcGIS user type to use actions and triggers (e.g. Creator).  The S123 green connector is an older version which is free to use (not a  premium) connector and is no longer maintained by Survey 123 team so any bugs are unlikely to be addressed there. All the actions and triggers are incorporated in the ArcGIS/ArcGIS Enterprise connectors. These are more advantageous especially with authentication and token exchange piece that can keeps your connection up to date. Also there are few new fixes and enhancements in them. Agree with @abureaux depending on business scale Power Automate premium license is a great purchase! It is worth it if the automation is going to effectively save you 1-2 hours a month of any resource(s) at minimum wage! 😄 Hope this helps. ... View more

@Bud Thanks for submitting the idea I will look more into it and what can be done. To start a power automate flow we will likely need a webhook in the Data Pipeline which can trigger. When Data Pipeline finished running, or something similar. But there could be other ways too.  Help me understand this better but I think the your use case can be solvable using Power automate in general. The construction project was entered correctly at the time the data was initially entered, but now it's out of date. This situation could not be avoided using editing constraints like an attribute rule, since the information was correct at the time it was entered. The only thing that has changed is: time has passed. We need to be notified by email about this issue so we can edit/update the data. Is it possible for you to create a stand a lone flow on recurrence that can use time difference formula to find the records and send an email. you might need to create tracking if the email is already sent or not otherwise it will start sending emails every time the flow runs.   ... View more

@IngridHogle Thanks for submitting this idea and letting us konw your use case. we do have a similar issue in our backlog and I will try to prioritize in our upcoming release. That said this needs to be be there in the output or fetch update changes deletions action instead. The trigger itself is for triggering the flow and will only return the changes url. The output of fetch should return the layerId. I think.   ... View more

@Bud  I am not sure what does the contact of yours mean by misfires. Just to be clear ArcGIS Power Automate connectors has nothing to do with webhooks being slow, not triggering or misfires. We are open to investigation if they have reproducible run.  I have seen many of our users use the use case you mentioned successfully with our triggers. You can choose to use the methods that works best for you. Like I said, workflow design is crucial when it comes to Power Automate. ... View more

@Bud Thanks for your question.  All the triggers related to Features/Attachments created, updated, deleted are server-side triggers. Currently, `when a survey response is submitted` trigger uses client-side approach (which may change in future) that are almost instant. S123 trigger is reliable for the amount of usage they get from all our customers. Yes, it has its shortcomings and issue 5 mentioned above is I think related to having too many fields in the request which Power Automate doesn't like. In the past, we have had issues with server-side webhooks through ArcGIS Online being slow to trigger.  Many of our users have previously complained that they didn't run reliably. Some of the issues issues you posted are associated with that, while some of them were related to outages in the Azure and our connector back-end last year. Others in-fact, were related to the webhooks performance. That said, we have worked with ArcGIS Online team and they have resolved the performance issues in the recently released ArcGIS Online version 2026.1. This has internally rehauled the architecture of  how the webhooks are triggered reducing previous bottlenecks. From my testing, the current server-side webhooks trigger within1-3 minutes. Please let us know if you experience is otherwise.  If this isn't acceptable time frame then there are ways to bypass the webhooks altogether in automation. That would add some overhead creating and maintaining the flows. It may or may not be for everyone.  So, can you rely on webhooks 100% of the time? I would say any technological system isn't flawless and there will be bugs and errors. Just because we have self-driving cars doesn't mean we completely let go of the steering; well at least not yet. I would recommend designing smart flows and think about how you can get notified and handle errors if and when they occur. This can include, Sending an email if the `Fetch updates, changes, deletion action` fails or setting up retries on actions if they fail the first time, etc. Lastly, we are here to help and improve, so please keep posting your thoughts, questions and comments. Here is a webhook troubleshooting guide our developer has put together if you wish to narrow down some of the common problems we have seen in the past   https://community.esri.com/t5/arcgis-connectors-for-power-automate-questions/guide-troubleshooting-arcgis-and-arcgis-enterprise/m-p/1634995#M1058 ... View more

@Bud Thanks for the nudge! The PaaS connector has been release as well so everything relevant is available in the PaaS connector. The article is now updated. ... View more

@OriGudes230175 Is this something you are looking for: Use the drill through feature—ArcGIS for Power BI | Documentation? ... View more

@SerjStol There aren't any changes from our end to the Survey response is submitted action this release.  It could be something changed from S123 side.  Does it happen to any Big Integer field? I will confirm if I can reproduce this. ... View more

@TimLohnes1 This looks fairly new, I do not see that toggle in my MS tenant and environment. Looks like new connection experience is on horizon. Thanks for this post, hope it will help others. ... View more