VS Code Debugging issue, show only single workflow as function even though there are multiple

Question

VS Code Debugging issue, show only single workflow as function even though there are multiple

Sumit Gaur 390

Hi,

i am building a logic app standard locally on vs code which has multiple workflows. when i try to debug this logic app locally it only shows me the first created workflow in the debug screen while the other doesn't show up in debug screen.

if you look the screenshot it only shows only the initial workflow as function during debugging while rest do not show up in here, even though they are in the repository.

what could be the reason that is causing this?

Screenshot 2023-11-15 171948_Lapp

MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-15T20:22:16.39+00:00

Sumit Gaur Thanks for posting your question in Microsoft Q&A. I am able to reproduce this issue and only first workflow created was showing up in the terminal window. Logic App (Standard) should support multiple and currently investigating this issue. Will get back to you shortly.
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-16T13:03:19.2166667+00:00

Sumit Gaur Can you share workflow.json for both workflows? and local.settings.json also if possible. (hide any sensitive info). That will be helpful to investigate exact scenario.

1 answer

Your answer

MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-15T20:22:16.39+00:00

Sumit Gaur Thanks for posting your question in Microsoft Q&A. I am able to reproduce this issue and only first workflow created was showing up in the terminal window. Logic App (Standard) should support multiple and currently investigating this issue. Will get back to you shortly.
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-16T13:03:19.2166667+00:00

Sumit Gaur Can you share workflow.json for both workflows? and local.settings.json also if possible. (hide any sensitive info). That will be helpful to investigate exact scenario.

Answer 1

MuthuKumaranMurugaachari-MSFT 22,446 Moderator

Sumit Gaur Using Azure Logic Apps (Standard) extension, I have created two workflows in my dev machine one with service bus trigger and another with HTTP request. Both workflows are showed in the Terminal console as shown below:

User's image

From your example, if you don't see Stateful1 workflow, then it is possible that a trigger is not configured in the workflow (or saved). Please validate and make sure a trigger is saved and reflected in the workflow.json (a workflow without trigger will not be displayed) for Stateful1.

If your workflow has trigger configured, then please open a new issue in LogicAppsUX repo with details such as Logic Apps (Standard) vs code version, Core tools version, Functions runtime version etc. along with workflow.json, local.settings.json. This will greatly help in reproducing the issue and right place to track the extension related issues (and fixes).

I hope this helps and let me know if any questions.

If you found the answer to your question helpful, please take a moment to mark it as Yes for others to benefit from your experience. Or simply add a comment tagging me and would be happy to answer your questions.

Sumit Gaur 390 Reputation points

2023-11-20T12:26:58.2966667+00:00

Hi @MuthuKumaranMurugaachari-MSFT i will check this git hub option i do see the trigger section in the workflow.json file so it is not an issue with that, if i copy that workflow and move it into a new logic app standard instance on vs code it starts working fine, i will do some more test and if nothing works out with above will raise a issue on the logic app repo.
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-20T13:52:37.3033333+00:00

Sumit Gaur sure and looking forward to your results. If you do end up creating a GitHub issue, let me know.
Sumit Gaur 390 Reputation points

2023-11-21T12:31:36.7166667+00:00

Hi @MuthuKumaranMurugaachari-MSFT now i am getting a different error without even touching anything, it is now not able to found any workflow at all.

No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-21T13:19:39.8633333+00:00

Sumit Gaur Sorry to hear that. Please open a new issue in LogicAppsUX repo with details such as Logic Apps (Standard) vs code version, Core tools version, Functions runtime version, workflow.json, local.settings.json etc. and our product team can investigate further. If possible, add a screenshot or share the full exception including stack trace, which will be helpful in investigating.
Sumit Gaur 390 Reputation points

2023-11-21T14:27:07.1766667+00:00

@MuthuKumaranMurugaachari-MSFT Ok, i got it fixed by deleting the local repo content and clone it back from the git, it now started to show it again, but looks like for SFTP trigger it doesn't show it in the debugging mode only for azure based provider like service bus, blob, request trigger etc. can you try with SFTP trigger when file is added or updated and then see what happens if it same for you i will raise an issue on the git repo.
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-21T16:45:33.96+00:00

Sumit Gaur Sure, Will review and get back to you.
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-11-22T12:22:24.6266667+00:00

Sumit Gaur I have tested with SFTP trigger action and the same has happened to me as well. Please file a new issue in GitHub repo as discussed.

Share via

VS Code Debugging issue, show only single workflow as function even though there are multiple

1 answer

Your answer