Logic Apps Dynamic Values not populating

Question

Logic Apps Dynamic Values not populating

Satoshi Nakamoto 45

Hi,

I created a Logic Apps flow last week and it was working perfectly for a few days. I've returned after the weekend and am now getting errors on the Dataverse and SQL Server actions (both displaying the error "failed to retrieve dynamic inputs. error details: '')

Logic Apps Connection Issue 4

Logic Apps Connection Issue 3

I've also tried to replicate the actions in a new flow, but the dynamic values aren't being populated:

Logic Apps Connection Issue 2

Logic Apps Connection Issue 1 The connections to both the Dataverse and SQL Server are showing as "Connected" so I'm really not sure what could be causing the issue.

Logic Apps Connection Issue 5

Satoshi Nakamoto 45 Reputation points

2023-07-10T15:48:29.4233333+00:00

Further to this, I'm also unable to connect to resolve the Azure Service Bus Queue - it also shows a blank list where there should be options.
Olivier Verplancke 0 Reputation points

2023-07-11T07:42:47.8066667+00:00

We had a similar behavioral issue, where our logic app was using a VNET integration to access our onprem urls for api access. In the designer screen we could however still access the servicebus using the connectionstring provided

On Friday July 7th, everything was working fine - on Monday July 10th (maybe earlier as well, but we have no records during the weekend) we noticed no messages being picked up anymore from our Azure ServiceBus queues.

No changes were done to our network from our ICT team. When I disabled the VNET integration - access to the ASB was fine (but the connection to our onprem environment obviously not). But when I re-enabled the VNET - the Logic App couldn't reach the queue anymore.

Long story short, in our case the solution was to enable internet access in our routing table.
Satoshi Nakamoto 45 Reputation points

2023-07-11T09:06:40.9933333+00:00

Hi @MayankBargali-MSFT I navigated to Code view then back to Designer, but I have no such option for "Generally Available Designer"
MayankBargali-MSFT 70,941 Reputation points Moderator

2023-07-11T10:43:10.0866667+00:00

@Satoshi Nakamoto What permission do you have on the logic app? Is this standard or consumption logic app. Can you check if anyone in your team has the contributor access/admin to verify if they see the option.
Tony Calcagni 10 Reputation points

2023-07-11T13:47:08.2366667+00:00

I am having the same problem..
James Pearsall 20 Reputation points

2023-07-11T18:07:18.5733333+00:00

I'm also having this exact same problem. It was working for an extended period until it suddenly stopped recently. Given the 7/10 date of this topic starting, it's conceivable the same service failure impacted us simultaneously.

Edit: Mine is a Standard app, not Consumption.
James Pearsall 20 Reputation points

2023-07-11T19:46:23.48+00:00

Update: Forcing use of "old designer" allows the design pane to work as previously expected. I have yet to run a test yet. There's a link on this help page on falling back to legacy designer:

https://purple-pebble-0e11de71e.1.azurestaticapps.net/tsg

I clicked that legacy designer link, authenticated into my azure session and was able to see a clean workflow. Again, I still need to test.
Ibrahim Syed 0 Reputation points

2023-07-12T00:14:40.4466667+00:00

Hi,

I have the same issue where SQL Server actions (both displaying the error "failed to retrieve dynamic inputs. error details: '')

I have quadrupled checked the connection and they are fine and showing as connected in the apiconnection.

Accepted answer

2 additional answers

Your answer

Satoshi Nakamoto 45 Reputation points

2023-07-10T15:48:29.4233333+00:00

Further to this, I'm also unable to connect to resolve the Azure Service Bus Queue - it also shows a blank list where there should be options.
Olivier Verplancke 0 Reputation points

2023-07-11T07:42:47.8066667+00:00

We had a similar behavioral issue, where our logic app was using a VNET integration to access our onprem urls for api access. In the designer screen we could however still access the servicebus using the connectionstring provided

On Friday July 7th, everything was working fine - on Monday July 10th (maybe earlier as well, but we have no records during the weekend) we noticed no messages being picked up anymore from our Azure ServiceBus queues.

No changes were done to our network from our ICT team. When I disabled the VNET integration - access to the ASB was fine (but the connection to our onprem environment obviously not). But when I re-enabled the VNET - the Logic App couldn't reach the queue anymore.

Long story short, in our case the solution was to enable internet access in our routing table.
Satoshi Nakamoto 45 Reputation points

2023-07-11T09:06:40.9933333+00:00

Hi @MayankBargali-MSFT I navigated to Code view then back to Designer, but I have no such option for "Generally Available Designer"
MayankBargali-MSFT 70,941 Reputation points Moderator

2023-07-11T10:43:10.0866667+00:00

@Satoshi Nakamoto What permission do you have on the logic app? Is this standard or consumption logic app. Can you check if anyone in your team has the contributor access/admin to verify if they see the option.
Tony Calcagni 10 Reputation points

2023-07-11T13:47:08.2366667+00:00

I am having the same problem..
James Pearsall 20 Reputation points

2023-07-11T18:07:18.5733333+00:00

I'm also having this exact same problem. It was working for an extended period until it suddenly stopped recently. Given the 7/10 date of this topic starting, it's conceivable the same service failure impacted us simultaneously.

Edit: Mine is a Standard app, not Consumption.
James Pearsall 20 Reputation points

2023-07-11T19:46:23.48+00:00

Update: Forcing use of "old designer" allows the design pane to work as previously expected. I have yet to run a test yet. There's a link on this help page on falling back to legacy designer:

https://purple-pebble-0e11de71e.1.azurestaticapps.net/tsg

I clicked that legacy designer link, authenticated into my azure session and was able to see a clean workflow. Again, I still need to test.
Ibrahim Syed 0 Reputation points

2023-07-12T00:14:40.4466667+00:00

Hi,

I have the same issue where SQL Server actions (both displaying the error "failed to retrieve dynamic inputs. error details: '')

I have quadrupled checked the connection and they are fine and showing as connected in the apiconnection.

Answer 1

@Satoshi Nakamoto Thanks for reaching out and Apology for the inconvenience due to this issue. As per the screenshot it looks like the Preview Designer.

Can you please navigate to logic app code view and then again click on logic app designer view, and you should see the Generally Available Designer. Please click on it and the designer should be back to the previous one. Please update the properties if needed and test it to confirm if you still observe the same issue.

Once confirmed that the issue is resolved I will also suggest you to leverage the File a bug option in the new designer so the product team can review it and fixed it. The issue might be caused due to the new designer and the product team is improving it as per the customer feedback and reported issue. User's image

In case if the general designer doesn't help you then please let me know so I can assist you further.

Update: I will reach out to the team for the issue in preview designer.

As James and Satoshi suggest you can us the fallback link to revert back to the old designer: https://aka.ms/lafallback

In case someone observe any issue with the new designer feel free to create the bug in this GitHub repo : https://github.com/Azure/LogicAppsUX/

James Pearsall 20 Reputation points

2023-07-13T21:04:38.83+00:00

Additional info: https://github.com/Azure/LogicAppsUX/issues/2949

Answer 2

Satoshi Nakamoto 45

James Pearsall has found the resolution.

Simply use this link to fall back to the legacy version of the Designer and all the errors disappear:
https://aka.ms/lafallback

James Pearsall 20 Reputation points

2023-07-12T17:41:07.5466667+00:00

That's great! It should be clarified that this is is a workaround and MSFT still needs to correct the underlying issue causing the new designer to fail.

Answer 3

Chandresh Sanghavi 6

I spent half day with our IT team. Great that using the version thru the link provided worked !!

But, there was no issue a day before (I did not change the designer or IT team did not change anything)..So, can we know what is being changed and why it stopped working ?

James Pearsall 20 Reputation points

2023-07-13T21:03:58.15+00:00

More information found here:

https://github.com/Azure/LogicAppsUX/issues/2949

"End of day" hotfix expected. Fingers crossed..
Chandresh Sanghavi 6 Reputation points

2023-07-13T21:18:02.7466667+00:00

I wish we get the fix sooner to start using the newer version.. because this old (working) version is lot lot slower !!!
Chandresh Sanghavi 6 Reputation points

2023-07-18T19:13:52.4333333+00:00

Are we having permanent fix deployed ? I am still having same issue using latest workflow (non fallback)..
James Pearsall 20 Reputation points

2023-07-18T19:17:52.0533333+00:00

I dumped my workflow and rebuilt it again as Stateless instead of Stateful. Some growing pains in that conversion but it's been working more reliably. This wouldn't help in all use cases, unfortunately.

I can't really confirm if that change was a direct cause of my recent luck or if it was just chance.
Chandresh Sanghavi 6 Reputation points

2023-07-18T19:33:12.19+00:00

I have to use Stateful workflow, because of the specific needs. Also, This is happening for brand new stateful workflow too. I also created new connection in workflow and still no luck on this. Basically, The API connection for managed identity fails to connect and bring the values for dropdowns.

On that ticket someone mentioned about deploying fix to all regions and no one has issues ? Strange, and very frustrating.. I have wasted almost 2 days on this and still waiting for the solution.

Share via

Logic Apps Dynamic Values not populating

2 additional answers

Your answer