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

Getting Unable to initialize Operation error on sql actions after deploying from one subscription to another subscriptions #5983

Open
vallamreddy1234 opened this issue Oct 29, 2024 · 3 comments

Comments

@vallamreddy1234
Copy link

vallamreddy1234 commented Oct 29, 2024

Describe the Bug with repro steps

  1. I have a logic app developed that has a several sql actions like create record and update record.
  2. I have created a sql connection using sql server authentication type.
  3. On the source subscription my sql actions are working fine.
  4. After i deploy the logic app, only the sql connections are not loading properly and giving an error "Unable to initialize Operation…." and are not allowing me to edit the actionImage

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

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

Image

Browser

I tried it on Edge and Chrome browsers. Behavior is same

Additional context

No response

@vallamreddy1234 vallamreddy1234 changed the title Getting Unable to initialize error on sql actions after deploying from one subscription to another subscriptions Getting Unable to initialize Operation error on sql actions after deploying from one subscription to another subscriptions Oct 29, 2024
@kipergil-wb
Copy link

Is there any update on this ?
We are also having the same error.

Azure portal session id: a9cf1806997f4632853abb26cabe636b
Logic App designer session id: undefined
Logic App designer instance id: N/A
Timestamp: Tue, 29 Oct 2024 13:35:39 GMT

@hartra344
Copy link
Contributor

@vallamreddy1234 can you please use the TSG to gather a har trace and error log? We're not going to be able to do much only looking at the information provided here. You can send the logs to laux@microsoft.com.

Copy link

github-actions bot commented Nov 1, 2024

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

@github-actions github-actions bot added the stale label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants