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

New to automate - anything to be wary of?

elpinguino

Hi community,

I've just gotten access to Microsoft Automate. I used to set up automations with Make/Integromat.

I've set up a flow so every time an S123 record gets submitted a row in an Excel table gets updated in Sharepoint.

Because I'm new to Microsoft Automate I wondered if there's anything I should be wary of? Like would is there the possibility it will eat up a lot of credits because the layer is always being watched?

Or does anyone have any good videos, templates or resources they recommend for Automate/ESRI users?

Najděte více příspěvků označených jako

Accepted answers

All comments

ahargreaves_FW

Token Timeout is presently 10 days. Meaning you need to re-sign in every week. @SeanKMcGinnis is working to extend those.

SeanKMcGinnis

Good day @elpinguino - the only thing you need to be wary of, for the next week or two, is the token timeout in general availability and GCC(low) is 90 days (it was previously 14 days and @ahargreaves_FW mentioned). The reason I say the next week or two, the most recent release has passed all internal and Microsoft testing and will be promoted to General Availability. With the new release, the refresh token issue has been addressed.

Regarding credit consumption, there are no credits used with webhooks or 'watching' the ayer. The credits being consumed are the same as all other transactions across ArcGIS Online.

For templates, there are many available to help you get started on the ArcGIS Connector for Power Automate details page. You will also be able to review the documentation for the connectors to help you understand what is going on.

Finally - this community is a great place to learn and share questions.

ahargreaves_FW

Hey Sean,

as this is SAAS will that 90 day version simply be an update that will happen on the cloud side? Or must end users do something? Is there a "token will soon time out" notification or is this a flow we must set up ourselves?

SeanKMcGinnis

All of it will happen on the backend with nothing for you to do. Currently Microsoft does not have monitoring capabilities, so it will still fall onto the flow owner to track the expiration. All things go to plan - you won't have to worry about it as it promotes into the tenant you are working in before the 90 day token expires.

RobertAnderson3

I just want to clarify, is this next update bringing a specific build up to the 90 days?

Or is the 90 day expiration going away completely? As in it will no longer expire?

elpinguino

This may be a stupid question, but so that means from the first time I set up a flow and sign in to Survey123/ArcGIS Online in Automate that's when the 90-day token starts, but this is planned to be fixed so I should set a reminder in my calendar 90 days from now just in case?

And I'll know there's an issue/token has expired if I notice the flow has failed?

SeanKMcGinnis

One of the first things to note - the Survey123 connector is managed by a different team and the initial token used to create the flow will time out in 14 days. Please check the Survey123 Community for more details.

Regarding the ArcGIS for Power Automate Connector, you will get notice that the flow has failed. You can set the reminder, but there is an exciting announcement that will be coming out early next week.

RobertAnderson3

I didn't realize the initial connector token for Survey123 times out after 14 days, that explains an issue I had last week. I've never had a timeout issue before but I guess I never signed into it again after building this new one. Interesting, thanks!

elpinguino

How did we all get on with this?

I found a spelling mistake in one of the field names in my excel spreadsheet in sharepoint (which the submitted survey123 writes into), so I updated the spelling. That has caused my flow to not run properly anymore. Not sure if this is related to the token updates discussed in this thread or the latest ESRI update, but Automate can't seem to find the survey, which it could do before the update. All the original parts of the flow other then the mispelling field name updates work fine. This could very well be an issue on my end though as I'm still finding my feet in Automate. Any pointers would be appreciated.

I tried testing in a new flow too.

AlagiriVenkatachal

Hi @elpinguino ,

This may be because the connection (token) may have expired for the Survey 123 trigger to ArcGIS Online and hence it is not able to retrieve the list of surveys into the dropdown. You can check the "Data" > "Connections" menu in Power Automate and find the Survey 123 connection, click the "..." to switch connection and re-authenticate with ArcGIS Online. This should potential fix this issue

RobertAnderson3

I had never once had issues with the token expiring until I started using the Create Report function, does the Survey123 token expire on a regular interval? Is it for the trigger or the Report action?

If it keeps expiring that really ruins a bunch of really cool flows I have built. If it is a defined 14 day timeout (that I don't see documented anywhere) are there plans to fix it like the ArcGIS connector Sean is speaking on?

Thanks!

elpinguino

Thanks for your reply @AlagiriVenkatachal . I work across a couple of ArcGIS Online accounts. We are using Survey123 in all of them. Once I made sure I was signed into the Survey123 for this account on another tab, and then checked my connection/ resigned in as you suggested above I was able to see the dropdowns I need. Automate may have thought I was trying to access a different AGOL accounts' S123.

NataliyaLys

I'm new to Power Automate, started using it over a month ago. I have a number of flows set up, all using ArcGIS online connector. Yesterday I noticed that all my flows failed. The errors that I got looks like token expiration issue.

I reset my ArcGIS online connection and 'resubmitted' each flow, and so I'm back to were I started. Kind of.

The problem is that I have some flows that get triggered when feaure is created. So even if I fixed the connection issue, I'm now left with features that were not updated by power automate (power automate assigns some values to features when they get created) and email with updates didn't get send, since the flow is triggered on feauture creation. I wonder if there is some work around for this.

Is there anyway to get notified then the token gets expired? Because if I wouldn't have checked, i would have never known that it expired. Hopefully in a day or two some of my users would have notified me that they are not getting emails, that power automate is supposted to sent then features are updated.

Appreciate any ideas suggestion on how to handle the token expiration issue.

Thank you.

Nataliya

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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