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

Flow faalt wanneer query geen resultaten oplevert

erica_poisson

Hallo @SeanKMcGinnis -

Ik heb 3 Flows die dagelijks draaien om een feature layer te controleren of aan bepaalde voorwaarden wordt voldaan. Als dat zo is, wordt er een e-mail verzonden. In veel gevallen zijn er geen records die voldoen aan de voorwaarden van mijn query. Wanneer dit gebeurt, falen de Flows. Ik maak me zorgen omdat ik niet wil dat de Flows automatisch worden uitgeschakeld door Power Automate nadat ze te vaak zijn mislukt. Ik heb een "escape" nodig zodat de hele Flow niet faalt wanneer mijn query niet wordt voldaan.

Hier is de fout die ik zie:

Je raadde aan dat ik deze oplossing probeer, maar het werkt niet ongeacht waar ik "configure run after to has failed" toevoeg.

Deze vraag werd oorspronkelijk gesteld in deze GeoNet-post hier.

Ik heb zo snel mogelijk een oplossing hiervoor nodig.

Dank je,

Erica

Vind meer berichten getagd met

Accepted answers

All comments

PhilLarkin1

Hi Erica

I wonder if it would be helpful to use the Terminate action. It is in the Control action group. It should give you the ability to exit the flow with the status Failed, Cancelled, Succeeded or custom value. I've not tested anything other than Failed so please post back if you attempt this.

PhilLarkin1

Also, in review of your last post, it seems you duplicated the query and set it to run after the fail of the first. If it is in fact the same query it should also fail.

Regardless, you'll need to signal to Power Automate that this isn't a problem even though the query returns no results. Hopefully this branch in your flow is an appropriate place to terminate the entire flow.

erica_poisson

Hi @PhilLarkin1 -

I realized I'd messed up the suggestion from Sean (re: duplicate query connector), but even after correcting my error that did not work.

As far as the Terminate control... I've actually never used this. I am curious where this would go in the flow.

Also, this morning I noticed some different behavior in the flows and I am wondering if @SeanKMcGinnis and his team have changed anything... I have no features which are returned on the query, however the flow doesn't fail like it was previously. When I check the flow results the outputs also look different than they did a few days ago. I've added two screen captures below for comparison. Now it looks like the ArcGIS Connector is OK with the fact that no results were returned from the query and the flow succeeds without failing.

Original error response received when no results returned:

New output when no results returned, flow succeeds:

PhilLarkin1

Great! Looks like the connector treats 0 records like a non-failed state. Seems like your problem is solved.

If you wanted to test Terminate you could set it to run after 'Get data from feature layer'. The status should be Canceled, Succeeded, or a custom value. I'm not sure if that allows for the flow to end in a non-failed state. Might be a something to try next time you find yourself in this situation.

SeanKMcGinnis

Good morning @erica_poisson & @PhilLarkin1,

To give you an update, the team was able to recreate the issue and create a backend solution that fix was pushed to production on October 4th.

This action now returns the results from the query, including 0 results, instead of failing as was previously occurring.

It seems like this is addressing the issue that you were encountering, but please let me know if you are still having issues.

erica_poisson

@SeanKMcGinnis -

Thank you.

Another issue has come up - I've received this error message out of the blue. Do I need to manually refresh my credentials every 14 days? This Flow ran fine on from the 4th to 7th after your fix was implemented, but failed all weekend.

If so, when will this be fixed? I do not need to do this with the Survey123 Connector. This is really awful if this is what I think it is...

SeanKMcGinnis

@erica_poisson, I am sorry you think the experience is really awful, but we are working with technology disparities between the different platforms. There is a difference in the way Microsoft and ArcGIS Online grants the refresh tokens and that is what is causing the tokens to expire after 14 days. We are actively working with the ArcGIS and Microsoft teams to come up with a resolution - it is one of our highest priorities.

The near term fix, which is planned to be included in the next release, is using a different OAuth method which will extend the refresh token to 90 days to give us additional time to work through a secure and sustainable solution between the different parties.

The reason you are not encountering this with Survey123 - the submitter's token is being included in the webhook payload. Since the ArcGIS Connector for Power Automate is not authenticating outside of the connection, there is no other way to get a token that can be passed securely given the permissions needed to edit a feature layer.

SeanKMcGinnis

@erica_poisson - I wanted to share an update with you. The recent published update to the ArcGIS Connector for Power Automate has extended the token timeout from 14 days to 90 days. We are continuing to have conversations with Microsoft to come up with a more permanent solution, but hopefully this helps.

erica_poisson

Hi @SeanKMcGinnis -

This is great news. While a permanent solution would be nice, 90 days is so much more reasonable for revisiting a flow to refresh the connection. Thank you for letting me know this has been implemented. The new connectors are really great and this new addition will make them even better.

Thank you!

PhilLarkin1

Thanks for your hard work. I'm glad ESRI is investing in this platform. Looking forward to new features.

Will you or someone from your team be presenting at the Developers Conference? Will schedule/presentation information be posted to the ArcGIS for Power Automate Blog, or maybe somewhere else?

AnthonyLatini

Hello everyone in this thread. @erica_poisson @PhilLarkin1 - I know it has been a bit since this has been updated, but in case anyone has missed it; token timeouts are no longer an issue in the ArcGIS Connector.

To remain logged in, a flow should run at least once within the given token timeout period. However, if an ArcGIS API key is used to create and maintain flows, there is no need to refresh the connection, as API keys do not require additional authentication once they are configured.

Please let me know if you have any questions!

Reference: Frequently asked questions—ArcGIS for Microsoft 365 | Documentation

PhilLarkin1

Thanks!

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.