Azure / Azure/LogicAppsUX

Run query and list results authentication hanging without presenting 403 error to UI

Open
#8,836 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
111
Forks
109
Avg merge
1d 23h
Merged PRs (30d)
20

Description

### Severity

P1 - Critical (Blocking production)

### Describe the Bug with repro steps

Expected behaviour:
The UI should present the 403 error within a modal in order to help the user diagnose and request necessary access to the requested resource from their system administrators.

Actual behaviour:
The UI does not present any errors whatsoever, and simply hangs whilst throwing infinite 403s to the chrome dev console.

Steps to reproduce:
1. Add a "Run query and list results" action.
2. Attempt to authenticate via the "Sign In" button.
3. Check console and witness errors thrown regardless of navigating away from the logic app designer.

### What type of Logic App Is this happening in?

Consumption (Portal)

### Are you experiencing a regression?

_No response_

### Which operating system are you using?

MacOS

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

Yes

### Workflow JSON

```json
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"contentVersion": "1.0.0.0",
"triggers": {
"Recurrence": {
"type": "Recurrence",
"recurrence": {
"interval": 1,
"frequency": "Day",
"timeZone": "Eastern Standard Time",
"schedule": {
"hours": [
0
],
"minutes": [
0
]
}
}
}
},
"actions": {
"Run_query_and_list_results": {
"type": "ApiConnection",
"inputs": {
"host": {
"connection": {
"referenceName": null
}
},
"method": "post",
"path": "/queryData",
"queries": {
"subscriptions": "",
"resourcegroups": "",
"resourcetype": "",
"resourcename": "",
"timerange": ""
}
},
"runAfter": {}
}
},
"outputs": {},
"parameters": {
"$connections": {
"type": "Object",
"defaultValue": {}
}
}
},
"parameters": {
"$connections": {
"type": "Object",
"value": {}
}
}
}
```

### Screenshots or Videos

_No response_

### Environment

- Browser: Chrome Version 145.0.7632.76 (Official Build) (arm64)
- Logic app type: consumption
Session ID: 202220e354914c4c942475cd65e0d5be
HubsExtension: 8ms | Version: 17.49.0.1
Microsoft_Azure_EMA: 9ms | Version: 2.60127.1.7
Microsoft_Azure_Resources: 29ms | Version: 1.111.0
Microsoft_Azure_Support: 30ms | Version: 1.625.20260131.1
Microsoft_OperationsManagementSuite_Workspace: 37ms | Version: 3.0.03313.2656

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue in the Logic Apps designer using the supplied workflow JSON: add the "Run query and list results" action, select Sign In, and inspect Chrome's console and network behavior. Trace the authentication failure and ensure the UI presents the 403 response in a modal instead of hanging or issuing repeated 403 requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, react, typescript
Domain
authentication, cloud, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.