Failed to retrieve dynamic inputs in Call a local function action after deployment

[mikhur]

Severity

P3 - Medium (Minor functionality affected)

Describe the Bug with repro steps

Follow the following steps to create a workflow in Visual Studio Code and deploy it to Azure.

1. Create and run .NET code from Standard workflows in Azure Logic Apps: https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions
2. Deploy to Azure https://learn.microsoft.com/en-us/azure/logic-apps/create-standard-workflows-visual-studio-code#deploy-to-azure
3. Open Workflow Designer in Portal
4. See "Failed to retrieve dynamic inputs. Error details: 'Encountered an error (InternalServerError) from host runtime.'" error message shown for the Call a local function in this logic app action
5. Go to Run History and Run the workflow
6. See it actually works there regardless of the error message in Designer

Expected behavior is not having the error message as above as that doesn't allow to make and save any changes in the workflow.

What type of Logic App Is this happening in?

Standard (VSCode)

Are you experiencing a regression?

no

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

It is in the attached zip files.

Screenshots or Videos

Environment

• Browser: Microsoft Edge 138.0.3351.121
• VS Code Version: 1.102.3
• Extension Version: Azure Logic Apps (Standard) 5.130.7

Additional context

• LogicAppWithCodeWorkspace.zip (VS Code Project)
• logic-app-issue.zip (Logic App Content)

[ccastrotrejo]

Hi @mikhur, Thanks for raising this issue and providing such detailed information, we really appreciate it.

We're aware of the problem and believe it may be related to a backend bug. I've already flagged it to one of our engineers, and we're actively working on a fix.

At the moment, this issue appears to only affect the designer experience. Running the logic app should still work as expected.

[swghimire]

We have identified the cause of the bug and have a fix in pr. We will hotfix this change as part of the current release. At this moment I do not have an exact timeline but once the pr is merged in I can provide a timeline.

[MattParkerDev]

Hi @swghimire, is there any update on this? :)

[swghimire]

@MattParkerDev This change would’ve been rolled out in the last release and we verified in portal it worked with that change. Is this still not working for you? What bundle version are you using?

[MattParkerDev]

https://github.com/Azure/LogicAppsUX/issues/8425#issuecomment-3430365720

This comment was the issue for me. It is not intuitive that moving the logic app folder will break this :)

[swghimire]

The dynamic properties use the projectDirectoryPath to be generated. The path to the lib/custom folder within your logic app is required to retrieve the schema we use to populate the dynamic functions and parameters. Moving that directory and not reflecting the folder change will mess up the way the runtime obtains the dynamic property. If this is something we need to document for users to know they need to reflect the change in both places, we can definitely do that.