Logic Apps Monitoring view - Unable to initialize operation

[rllyy97]

What is the issue?

On the Logic Apps monitoring view / when opening a workflow run, users may see some actions fail to initialize, showing an error message like the following:

"Unable to initialize operation …"

This should happen on operations that have connections with app settings values.

We know why this is happening, but we are still looking into what change might have caused this all of a sudden.

What is being done to fix it?

We are currently working on a fix for the issue and are expecting to release it in a hotfix sometime this week.

Thank you for your patience as we work to get this resolved!

[billchesnut]

Do you have any updates on this? It is starting to really impact my development efforts because I am working inside a VNET.

[ccastrotrejo]

Hey @billchesnut yes, we have made the fix for this issue, and we have started the rollout of it. As for now could you please use this private link for portal, this environment should contain the fix for it? Azure Stage 1

[billchesnut]

thanks, that is working

[rllyy97]

Quick status update, we are almost halfway through the fix rollout, we should reach all stages by EoD Friday

[rllyy97]

The fix for this issue should be live in all production regions, closing this issue.
If anyone is still facing the issue try clearing your cache to pick up the new version.
If you clear the cache and still have issues please leave us a comment and we will investigate further!

[las3r]

Thanks for being so quick with a fix. The problem however hasn't fixed for me. I have even used google chrome to check (I don't use chrome), just to make sure it wasn't cache on my side. For me it's the same as it was in #5963.

[RobJoosen]

Hi, Same here:

[ccastrotrejo]

Hi @RobJoosen and @las3r
Do you see any error in the console log or in the network tab? Do you have writing permissions in the logic apps that you are trying to take a look?
The mentioned fix was intended to solve the parameterization of appsettings and avoid unresolved parameterization in the API calls like this

[las3r]

I have the right writing permissions (owner).

Simple keyvault "get secret" action (Based on an api connection) - error from the console:

{
    "schemaVersion": 1,
    "extractionType": "FxError",
    "message": "Unable to initialize operation details for swagger based operation - Get_secret. Error details - Operation Id cannot be determined from definition and swagger",
    "name": "MsPortalFx.Errors.Error/Error",
    "stack": "    at https://portal.azure.com/Content/Dynamic/cD7e6jg6jXHe.js:1:273594\n    at Array.forEach (<anonymous>)\n    at https://portal.azure.com/Content/Dynamic/cD7e6jg6jXHe.js:1:273549\n    at https://portal.azure.com/Content/Dynamic/Qu8SkCtRv2c_.js:19:2582\n    at Array.filter (<anonymous>)\n    at t.FunctionProxyImpl._flushCallQueue (https://portal.azure.com/Content/Dynamic/Qu8SkCtRv2c_.js:19:1962)\n    at r.onmessage (https://portal.azure.com/Content/Dynamic/Qu8SkCtRv2c_.js:19:1285)",
    "blade": {
        "id": "Extension/Microsoft_Azure_EMA/Blade/DesignerEditorConsumption.ReactView",
        "instanceId": "Blade_ca62b9d0c9134203877ca6af010b395f_14_0"
    },
    "online": true
}

and my event grid trigger action - error from the console:

{
    "schemaVersion": 1,
    "extractionType": "FxError",
    "message": "Unable to initialize operation details for swagger based operation - When_a_CustomerCaseCommentUpdate_event_occurs. Error details - Operation Id cannot be determined from definition and swagger",
    "name": "MsPortalFx.Errors.Error/Error",
    "stack": "    at https://portal.azure.com/Content/Dynamic/cD7e6jg6jXHe.js:1:273594\n    at Array.forEach (<anonymous>)\n    at https://portal.azure.com/Content/Dynamic/cD7e6jg6jXHe.js:1:273549\n    at https://portal.azure.com/Content/Dynamic/Qu8SkCtRv2c_.js:19:2582\n    at Array.filter (<anonymous>)\n    at t.FunctionProxyImpl._flushCallQueue (https://portal.azure.com/Content/Dynamic/Qu8SkCtRv2c_.js:19:1962)\n    at r.onmessage (https://portal.azure.com/Content/Dynamic/Qu8SkCtRv2c_.js:19:1285)",
    "blade": {
        "id": "Extension/Microsoft_Azure_EMA/Blade/DesignerEditorConsumption.ReactView",
        "instanceId": "Blade_ca62b9d0c9134203877ca6af010b395f_14_0"
    },
    "online": true
}

Other:

{
    "designerVersion": "4.105.8",
    "designerID": "B4DC8745-AC38-4CD0-9C62-FF9F6CD7DC3C"
}

Please note that my previous case was closed (#5963) in favor of this "rollup" issue here, but it seems they are two specific (and different) issues.

[sdk11DB]

Hi,
I am facing the same issue as this.

[ccastrotrejo]

Ok, thanks for letting me know. @las3r I will reopen yours and take a further look, I will try to repro and answer back on that issue thread.

@sdk11DB do you get any console or network errors while doing this?

[RobJoosen]

As an additionL I noticed this behaviour in Consumption Logic Apps as well....

[sdk11DB]

Ok, thanks for letting me know. @las3r I will reopen yours and take a further look, I will try to repro and answer back on that issue thread.

@sdk11DB do you get any console or network errors while doing this?

I do not see any run time errors or network errors. The flows run without any issues. It is only when I try to open in edit, it comes like this with the issue.

[sdk11DB]

Ok, thanks for letting me know. @las3r I will reopen yours and take a further look, I will try to repro and answer back on that issue thread.
@sdk11DB do you get any console or network errors while doing this?

I do not see any run time errors or network errors. The flows run without any issues. It is only when I try to open in edit, it comes like this with the issue.

Hello, any update on this ? I still have the issue.

[las3r]

@sdk11DB this is further discussed in #5963.

[ccastrotrejo]

Hi @sdk11DB

Is there any chance we can get your workflow json schema from your logic app? The error from @las3r seems really specific to their workflows, and would be good if yours is because of the same reason. Thanks!
You can share it with me to my email [email protected]

[ebytreesa]

Hi, I am facing the same issue. I get a console error like this

"Unable to initialize operation details for swagger based operation - Create_or_update_document_(V3). Error details - Operation Id cannot be determined from definition and swagger"

[ccastrotrejo]

Hi @ebytreesa, Is there any chance we can get your workflow json schema from your logic app? You can share it with me to my email [email protected]

[ebytreesa]

Hi @ebytreesa, Is there any chance we can get your workflow json schema from your logic app? You can share it with me to my email [email protected]

Hi @ccastrotrejo, I’ve emailed you the workflow JSON schema from a different address

[ccastrotrejo]

Hi @ebytreesa , could you please send it again? It seems that I couldn't receive your email

[ebytreesa]

Hi @ebytreesa , could you please send it again? It seems that I couldn't receive your email

@ccastrotrejo I have sent it again.

[ebytreesa]

@ccastrotrejo Any update on my issue?

[ccastrotrejo]

Hi @ebytreesa I replied to you via email with a couple of follow up questions. Whenever you have a chance, could you please answer back?

[ebytreesa]

Hi, I couldn’t open the attatchment in the other email. Can you send it again?

[ccastrotrejo]

Hi @ebytreesa this is just an email that GitHub sends whenever we comment in the GitHub issue. I am not able to see your email. But here are the follow up questions:
Does this work in old designer and doesn’t work in the new one?
Do you get any errors in the network tab?
Do you happen to know what is the complete error message that the action is throwing when loading the new designer?

[ebytreesa]

Hi @ccastrotrejo, It was working in the old designer. It is not there anymore. We don’t get any error in the network tab. The error message that the action is throwing is ‘unable to initialize operation’, similar to the pictures posted by others.

[ccastrotrejo]

Hi @ebytreesa I am still not repro this issue. I copied the workflow schema you shared with me but couldn't repro. Although I see some logs with the error on our side, which is something really weird.
Do you mind sharing with me again the workflow.json and some HAR log traces while you trying to open designer? Here is a small guide on how to get the HAR file. collecting-network-logs-in-a-har-file

Pleas share does files with me to my email. [email protected]

[mramott]

Hi @ccastrotrejo. We are also experiencing this issue. We have a workflow that calls a Document Intelligence custom model analyzer. It is triggered from another logic app and works fine, but then randomly stops working and fails on every subsequent run. Upon inspecting the the workflow, the previously-quoted error is displayed on the relevant step:

"Unable to initialize operation details for swagger based operation - step here_. Error details - Operation Id cannot be determined from definition and swagger."

Deleting and replacing the step solves the issue, only for it to recur at a random time later.

I'm hoping I may be able to email you logs and our workflow.json for a closer look. If this is possible, please do let me know (with my advance thanks.)

EDIT 29/11: The behaviour we are seeing and the steps to resolution for the DI connector are effectively identical to the below report by JoeHague86, including the breaking of the step after several days of normal operation and the inability to select the connector when it is broken. In one instance, I actually moved the broken connector into a conditional which never ran, and several days later, the original connector had moved back to a normal state, while its replacement (a new DI connector I had created to 'fix' the issue) had broken with the above error.

[JoeHague86]

I am also still having this issue. The logic app worked fine initially but seemingly after a few days it starts to fail, additionally when editing you cannot select the connector in its broker state. If I delete the DI connector and run again it works fine... for a while. But this is arduous and requires significant refactoring in the logic app. Do we have an update on this bug? It should be noted that this is happenning on both the document recogniser and the extraction connectors.

[ccastrotrejo]

Hi @JoeHague86 thanks for raising this issue.

• Do you see any issues in the console tab?
• Does your connection use settings parameterization?

[JoeHague86]

@ccastrotrejo

This is all I get when clicking on the connector when viewing the run, I am not using any specific settings parameterisation. The loading wheels persist no matter how long I wait. In the editor the same thing happens exactly. The only way I can get it to work is to delete the docInt connectors, re-insert and then refactor the subsequent code which uses their outputs

[ccastrotrejo]

Hi @JoeHague86
Do you mind sharing with me again the workflow.json and some HAR log traces while you trying to open designer? Here is a small guide on how to get the HAR file. collecting-network-logs-in-a-har-file

Pleas share does files with me to my email. [email protected]

[clb900528]

Hi @ccastrotrejo Is there currently a solution to this issue?

[ccastrotrejo]

Hi @clb900528 it seems that the issue is related, however its quite hard to determine what is going on, if indeed its related or if there is an already implemented solution to it. Could you please create a new GitHub issue detailing what is happening in your logic app? You can do that here https://github.com/Azure/LogicAppsUX/issues