Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow not deployed to portal after successful deployment. #4793

Open
v82abhishekverma opened this issue May 7, 2024 · 0 comments
Open
Assignees
Labels

Comments

@v82abhishekverma
Copy link

Describe the Bug with repro steps

I am using Azure Logic App Standard extension v4.13.2. Developed the stateful workflow locally using Visual Studio Code. Deployed to Azure using VS code. Output window show deployment successfully, connection and parameter file deployed but workflow is missing. I cant see workflow on portal.

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

I am using Azure Logic App Standard extension v4.13.2. Developed the stateful workflow locally using Visual Studio Code. Deployed to Azure using VS code. Output window show deployment successfully, connection and parameter file deployed but workflow is missing. I cant see workflow on portal.

FYI.. When I rolled back to v2.81.5 which I was using until last Friday, I able to deploy the workflow successfully.

Seems V4.x.x got bug.

AbhishekVerma1982_0-1714754428150

Browser

Chrome

Additional context

I am using Azure Logic App Standard extension v4.13.2. Developed the stateful workflow locally using Visual Studio Code. Deployed to Azure using VS code. Output window show deployment successfully, connection and parameter file deployed but workflow is missing. I cant see workflow on portal.

FYI.. When I rolled back to v2.81.5 which I was using until last Friday, I able to deploy the workflow successfully.

Seems V4.x.x got bug.

@ccastrotrejo ccastrotrejo self-assigned this May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants