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

Nelze získat feature layers při nastavování ArcGIS Connector v Microsoft Power Automate

KevinMantels

Snažím se vytvořit nový automatizovaný cloudový tok v Microsoft Power Automate pomocí konektoru ArcGIS for Power Automate a jeho dostupných triggerů. Bez ohledu na to, který trigger použiji, když se pokusím vybrat feature layer, který má být sledován, obdržím následující chybovou zprávu: "Nelze získat hodnoty. Požadavek na dynamické volání selhal s chybou: Neočekávaná chyba při volání APIHubsRuntime API: ...". Snímek obrazovky s chybovou zprávou je níže.<\/P>

Potvrdil jsem, že konektor ArcGIS for Power Automate má správné přihlašovací údaje pro můj účet ArcGIS Online a je připojený. Mám prémiový účet Power Automate, takže i když je ArcGIS prémiový konektor, nemyslím si, že by to byl problém. Používám Power Automate ve vládním prostředí a všiml jsem si, že konektory dostupné v mém vládním účtu jsou omezené ve srovnání s těmi dostupnými v komerčních účtech, ale nejsem si jistý, zda by to mohlo způsobovat tyto problémy. Nakonec, pro úplnost, jsem schopen vytvářet toky s konektorem Survey123 bez jakýchkoli problémů. Uvědomuji si, že jsou to dva zcela odlišné konektory, ale zmiňuji to pro případ, že by to bylo relevantní.<\/P>

Nejsem si jistý, jestli mi něco neuniklo v krocích nebo nastaveních. Konektor Survey123 fungoval ihned po instalaci, takže jsem předpokládal, že konektor ArcGIS bude také. Zkrátka nemám momentálně žádné další nápady na řešení problémů. Jakákoli pomoc by byla velmi oceněna.<\/P>

<\/span><\/P>

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

Accepted answers

All comments

SeanKMcGinnis

Hello @KevinMantels - Since you are in the first step of establishing the webhook, it does not appear you are missing any steps. The thing I am noting is that it is a .NET error with a number of 'Azure' references and not one that is being thrown by the ArcGIS Online Connector for Power Automate. Because you are in GCC may be adding a wrinkle, but it tough to fully tell from the truncated error message.

Could you please submit a support ticket? That way we can get additional people involved to try and figure out the source of the issue.

SeanKMcGinnis

Hi @KevinMantels

I was talking with one of the product developers trying to figure out what the issue might be and noticed the 504 error. It raised the question, how many layers do you own?

KevinMantels

@SeanKMcGinnis, great catch!! The account I was attempting to use with the connector has ~225+ layers. I tried using a different AGOL account with a minimal number of layers and the connector worked perfectly. Thank you for noticing and pointing out this issue--I never would have thought of it.

For my future reference, is there a specific maximum number of layers that is permitted before the connector will no longer work correctly and result in this error? I'm just trying to determine if our organization may need to take steps to ensure that the Power Automate connectors continue to work properly.

SeanKMcGinnis

@KevinMantels - I am glad you did the additional testing to and saw that it worked in an organization with fewer records. Unfortunately, we do not have an estimated number of layers in an organization and then things get weird. We have tested it in organizations with 1000+ layers and it works. My personal organization has over 500 layers and it works. Since you are working with ~225 layers and having an issue, that breaks our assumption that it is a sheer volume/count is a limiting factor.

If you do not mind, there are two things we can do to test and see if we can get them to be successful or throw a more meaningful error.

1. Try to use the 'Get data from feature layer' action to see if that returns the list of feature layers in your organization.

Screen Shot 2022-08-11 at 11.46.55 AM.png

2. Instead of picking the feature layer from the dropdown, paste the Item ID into the field and see if that will grab the layer and let you build the rest of the flow

I am adding @Pavel148 to this thread and he may be able to help us out further.

KevinMantels

@SeanKMcGinnis - just to clarify, both of the AGOL user accounts I tested on are in a single organization. I'm not sure if it's relevant but I just wanted to mention. The 225 layer count is for my personal user account, but the organization as a whole has around 450 layers total. The second user account I tested on has only one layer.

Following up on your suggestions:

1. Try to use the 'Get data from feature layer' action to see if that returns the list of feature layers in your organization.

This unfortunately still resulted in an error message that appears to be the same as the one I received previously. In addition to the below screenshot I am also pasting the entire text of the error message in the hope that it may be useful.

Could not retrieve values. The dynamic invocation request failed with error: Unexpected error occurred when calling the ApiHubsRuntime API: 'Microsoft.Azure.ProcessSimple.Data.Entities.Exceptions.ProcessSimpleDataException: The ApiHubsRuntime API call failed with http status code 'GatewayTimeout' and response content '{
"error": {
"code": 504,
"source": "power-apis-usgov001-public.azure-apihub.us",
"clientRequestId": "98e36f30-2783-4a96-acbc-68379e35fe7d",
"message": "The response is not in a JSON format.",
"innerError": "<html><head><title>504 Gateway Time-out</title></head><body><center><h1>504 Gateway Time-out</h1></center></body></html>"
}
}'
at Microsoft.Azure.ProcessSimple.Data.DataProviders.AzureResourceManagerDataProvider.<>c__DisplayClass52_0`2.<<CallAzureResourceManager>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.Azure.ProcessSimple.Data.DataProviders.AzureResourceManagerDataProvider.<CallAzureResourceManager>d__52`2.MoveNext()'.

2. Instead of picking the feature layer from the dropdown, paste the Item ID into the field and see if that will grab the layer and let you build the rest of the flow

This DOES work. I was able to successfully build and test a flow using this method. To be specific--it worked with the connector tied to my personal AGOL account with the 225 layers, which makes it a successful workaround for us going forward. Thanks so much for suggesting this option.

Esteban_Leguizamo

Any updates on this problem. I am trying to automate some processes and the PowerAutomate does not work even with the templates provided.

JessMiller1

Has there been any movement with this issue? I'm having the same issue and can't seem to connect to anything! I'm also in the GCC licensing, but not High. Please help! Error posted below.

Could not retrieve values. The dynamic invocation request failed with error: Unexpected error occurred when calling the ApiHubsRuntime API: 'System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass47_3`2.<<CallService>b__2>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 580 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.WindowsAzure.ResourceStack.Common.EventSources.IHttpEventSourceExtensions.<TraceHttpOutgoingRequest>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass47_1`2.<<CallService>b__0>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 566 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<CallService>d__47`2.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 493'.

AnthonyLatini

Hello all. I have been working with our internal Support team on this issue and we are investigating it. Please hold tight while we gather the appropriate information and determine a path to rectify this issue. Thank you.

DominicRobergeIADOT

here's another post of connection issues

https://community.esri.com/t5/arcgis-for-power-automate-questions/issue-retrieving-feature-layer-using-template/m-p/1347816#M436

AnthonyLatini

Thank you for the link @DominicRobergeIADOT . My colleague @Pavel148 and I are looking into that thread as well as a few others that are experiencing this issue.

AnthonyLatini

@DominicRobergeIADOT @KevinMantels @JessMiller1 @Esteban_Leguizamo - Good afternoon, all. My colleague @Pavel148 and I have pushed out an update that should resolve this issue.

Please test your flows and let me know if you are still experiencing this issue. As a note, the errors that are shown in this thread are slightly different than the error that was being displayed in this thread: Solved: Re: issue retrieving feature layer using Template - Esri Community

JessMiller1

Thank you for checking out this issue! Unfortunately, it still won't populate anything for me. It takes a long time to load the value, then nothing. Here's my error still...

Could not retrieve values. The dynamic invocation request failed with error: Unexpected error occurred when calling the ApiHubsRuntime API: 'System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass47_3`2.<<CallService>b__2>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 580
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.WindowsAzure.ResourceStack.Common.EventSources.IHttpEventSourceExtensions.<TraceHttpOutgoingRequest>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass47_1`2.<<CallService>b__0>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 566
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<CallService>d__47`2.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 493'.

AnthonyLatini

Thank you for the update @JessMiller1 . This error is slightly different than the one that was resolved. We are still looking into this error as well.

Two quick questions on this:

1. Does this error still occur in an incognito/private window?

2. Does this happen in your account or multiple ArcGIS accounts in your organization?

Krocha

Hello @AnthonyLatini, I am still experiencing the same issue. It does not let me copy the error message only screenshot it. I also tried it through a private browser but same error issue. I have created a previous flow using ArcGIS connector and it works fine but for some reason i cannot create a new one using ArcGIS connector since the layers wont load.

Screenshot_5-12-2024_133453_make.powerautomate.com.jpeg

JessMiller1

I just want to update that this never worked for me, no matter how many different things I tried. So I just moved on and stopped trying, sadly. I went another direction that was more complex. Would've loved if this worked!

Akshay Harshe

@JessMiller1 it is probably late to respond on this thread, regardless, were you ever able to get this to work? We have fixed several issues since then and couple others are in the pipeline if you are using a Feature layer with data referenced from enterprise cloud database. Apologies for any inconvenience. If you still see the error, please reach out and we would love to discuss further on the issue.

Please remember Power Automate needs access to the resources to create workflows and firewalls can also block them. Secondly, make sure to use `Fetch Change, updates...` right after the trigger to retrieve the change from the trigger/webhook.

Jamie_Leitch_CNF

@AkshayHarshe I just received this error today on a power automate flow that had been working before today. Any solutions for it?

NataliyaLys

My ArcGIS connection in Power automate started dropping today as well. And I cannot re-add connection in any of my flows.

Akshay Harshe

@NataliyaLys We are experiencing some issue today and we are investigating the issue at the moment.

Jamie_Leitch_CNF

Hi @NataliyaLys , Are you seeing any errors? My ArcGIS Get data from feature layer step in my flow times out after 7 retries with GatewayTimeout errors.

NataliyaLys

@Jamie_Leitch_CNF When I click on ArcGIS Connection details this is an error that I see: Failed to refresh access token for service: oauth2generic. Correlation Id=060bdd10-4b4e-1d38-dc39-ab2040cfae25, UTC TimeStamp=6/9/2025 7:59:10 PM, Error: OAuth 2 access token refresh failed. Access token request to https://unitedstates-002.azure-apim.net/proxy/api/authentication/oauth2/token failed. Client ID and secret sent in form body. Details: A task was canceled.. Response status code=InternalServerError. Response body:

If I click 'Reconnect' it appears to reestablish connection, but my flows still fail. And if I try to fix connection within a flow it just spins and it never gives me a list of feature services from my content.

Jamie_Leitch_CNF

@NataliyaLys I'm seeing the same. Also when I go to the Connections page in Power Automate, I see this:

And when I click Reconnect, a window pops up and appears to sign into AGOL again and in shows "Connected" on the connections page. The page will shows "Reconnect" again if I refresh it after a while.

ArcGIS Online health dashboard shows no issues and MS Power Platform shows no issues either.

Akshay Harshe

Hi @Jamie_Leitch_CNF There has been an issue with the ArcGIS for Power automate containers since this morning, we are working hard to get to the bottom of the issue. We are sorry for the inconvenience this has caused.

CORFOPYM_Ingenieria

I have the same problem, please help.

Jamie_Leitch_CNF

@AkshayHarshe I just did a test with one of my flows and it seems the issue is resolved - thanks!

Jamie_Leitch_CNF

@CORFOPYM_Ingenieria try testing it today, I believe they fixed this.

CORFOPYM_Ingenieria

Thanks, it's working now

Jamie_Leitch_CNF

I created a flow in MS Power Automate to hopefully mitigate any more issues with this. Here is what I did.

Create a cloud flow that is triggered by Recurrence and set it to run daily.
Add a step for ArcGIS - Get data from feature layer.
Choose a feature layer from your content that will never be removed.
Add a Scope Control action and configure the Run after settings to be: has failed, is skipped, has timed out.
In that Scope Control add a "Send email" action to email yourself. This way, if the connection to ArcGIS times out or fails, you will get an email. When successful, this shoulda also update the security token for the ArcGIS Connectio.

hopefully this helps

DaveAlmond

I was having the issue where the 'Layers in' layer list would not dynamically populate and the connector (ArcGIS Enterprise, Create a record in a feature layer) would raise the 'Could not retrieve values' error + the stack trace. Instead of selecting 'My Contents/My Groups/My Organization' for the 'Layers in' parameter, I favorited the target layer in Portal->My Content and chose 'My Favorites' for the 'Layers in' parameter, which solved the issue of connecting to a multi-layer feature service for me.

Initially, the 'Create record in a feature layer' action only allowed me to enter the Item ID of the target layer since the dynamic layer-picker would not load (and raised the 'Could not retrieve...' error). Entering the Item ID as a custom value in the Feature Layer parameter would show me the correct feature layer's attribute fields (in a two-layer feature service), but the flow failed and raised the error that the Layer ID was not passed to the request. Once I set the 'Layers in' parameter to Favorites, the connector distinguished between Layer 0 and Layer 1 in the request, which solved my issue.

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.