Additional .NET WorkflowActionTrigger Functions not registering

[brad302]

Describe the Bug with repro steps

I can't guarantee steps for being able to reproduce, I can merely demonstrate.

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using new designer or old designer

New Designer

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

Yes

Workflow JSON

No response

Screenshots or Videos

Browser

Chrome

Additional context

Originally, when I was creating the WorkflowTrigger functions, they would appear in the list and able to be selected from.

After compilation, restarting VS Code, changing the affected workflow, clearing the lib folder, etc. etc. ... new functions won't appear in the list to be selected from. This also results in a lack of clarity on the parameters.

I workaround it by specifying manually but it's just not ideal.

AB#26105047

[hartra344]

@ccastrotrejo can you bring this up with the backend engineer? It looks like there may be some API issues happening here.

[ccastrotrejo]

Yes, I will contact BE team

[ccastrotrejo]

Hi @brad302 I talked with the BE team, in order to confirm this is a bug and keep forward with the investigation could you please send us the code and function.json from the functions that are not showing up in the dropdown selector? So far AppendArrayToAnotherArray and ConvertObjectArrayToSinglePropertyPrimitiveArray are the ones I can identify.

Please send the files to my email. ccastrotrejo@microsoft.com

Also if there is any sort of error when debugging (pressing F5) the functions or logic apps, please share it as well

[brad302]

@ccastrotrejo email sent, thanks again for the prompt replies (@hartra344) ...! I'm really liking the product so far, have been dealing with consumption for years but the additional features of standard make it a great product. Keep up the good work.

[swghimire]

@brad302 thank you for sending over the zip file of your project! I was able to get all of the functions to appear when I ran it on my end. One thing I noticed is you have a function.sln in your project that solutions file can cause conflicts with the workspace. Another thing I would do is copy the full file path from right clicking the \LogicApp folder so something like "C:\Users\\long-service-leave\Workspace\LogicApp". Then replace theProjectDirectory value in your workflow-designtime\local.settings.json just to help with locating the functions better in case ProjectDirectory attribute was misgenerated.

Make sure the file path has double backslashes but it should looks something like this:

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsSecretStorageType": "Files",
    "FUNCTIONS_WORKER_RUNTIME": "node",
    "ProjectDirectoryPath": "C:\\Users\\name\\long-service-leave\\Workspace\\LogicApp",
  }
}

Let me know if you need any help or if that did not resolve your issue!

[brad302]

YES!!! Thanks for the help, it was the path in the local.settings.json that you mentioned. It was pointing to an old folder. A trap for young players. I'll keep that in mind if it ever happens again,

Once again, thanks for your help @swghimire and @ccastrotrejo ...!

[brad302]

@swghimire ... this may be one of interest to you as well ... it's been sitting open for a while now ... https://github.com/Azure/logicapps/issues/937