Reported issues for logicapps-mcp

Pod holds 16 of 71 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to logicapps-mcp.

Most discussed

Add workflow state to listRunHistory response

Feature Request

Add the workflow's current state (Enabled/Disabled) to the run history response.

Use Case

When debugging why a workflow hasn't run recently, it's useful to know if the workflow is currently disabled without making a separate API call.

Current Response

{ runs: [{ id, name, status, startTime, ... }] }

Proposed Response

{ runs: [...], workflowState: "Enabled" | "Disabled" }

Files

src/tools/runs.ts - listRunHistory function

Part of #89

Read the thread · 2026-01-07 · open · 1 comment

Cache TTL from settings is not applied

Problem

setCacheTtl() is exported from src/tools/shared.ts but is never called during initialization. The loadSettings() function in src/config/settings.ts loads cacheTtlSeconds from environment/config, but this value is never passed to setCacheTtl().

Impact

The LOGICAPPS_MCP_CACHE_TTL environment variable has no effect - cache always uses the hardcoded 5-minute default.

Solution

Call setCacheTtl(settings.cacheTtlSeconds) during server initialization after `loadSetting

Read the thread · 2026-01-07 · closed · 1 comment

Add get_runs_by_failed_action tool

Feature Request

Add a tool to find all workflow runs where a specific action failed. This is a common debugging pattern.

Use Case

Show me all runs where the Send_Email action failed
Find runs where the SQL query timed out

Proposed API

get_runs_by_failed_action(subscriptionId, resourceGroupName, logicAppName, actionName, workflowName?, top?, startTime?, endTime?)

Implementation Notes

Would need to:

List runs (with optional date filter)
For each run, check if the specifi

Read the thread · 2026-01-07 · open · 1 comment

testConnection doesn't use retry logic

Problem

\ estConnection\ in \src/tools/connections.ts\ uses raw \etch()\ instead of \etchWithRetry()\ when calling the connection test endpoint.

Impact

Transient network failures or rate limiting during connection tests won't be retried, leading to false negatives.

Solution

Use the existing \rmRequest\ or extract \etchWithRetry\ and use it for the test call.

Files

\src/tools/connections.ts\ lines 157-183 (testConnection function)

Part of #90

Read the thread · 2026-01-07 · closed · 1 comment

listSwagger POST endpoints may need empty request body

Problem

The \listSwagger\ and \listExpressionTraces\ POST endpoints are called without a request body, but Azure APIs sometimes require at least an empty object \{}\.

Impact

May cause sporadic 400 Bad Request errors on some Azure API versions.

Solution

Pass \ody: {}\ to POST requests that don't have explicit body content.

Files

\src/tools/swagger.ts\ lines 51-55 (listSwagger)
\src/tools/expressions.ts\ lines 107-111 (listExpressionTraces)

Part of #88

Read the thread · 2026-01-07 · closed · 1 comment

HTTP mode missing passthrough token injection

Problem

The HTTP server mode in \src/http/index.ts\ doesn't extract the Authorization header and call \setPassthroughToken()\ before handling MCP requests.

Impact

All tool calls in HTTP mode will fail with 'Bearer token required' error because the passthrough token is never set from the incoming request's Authorization header.

Solution

In \handleMcpPost\, extract the Bearer token from \ eq.headers.authorization\ and call \setPassthroughToken()\ before processing, then \clea

Read the thread · 2026-01-07 · closed · 1 comment

Standard run actions missing pagination

Problem

\getRunActionsStandard\ in \src/tools/runs.ts\ doesn't follow \ extLink\ pagination when listing run actions.

Impact

Workflows with more than 100 actions will have truncated action lists, making debugging incomplete.

Solution

Use \workflowMgmtRequestAllPages\ instead of \workflowMgmtRequest\ for the list endpoint.

Files

\src/tools/runs.ts\ lines 366-371

Part of #89

Read the thread · 2026-01-07 · closed · 1 comment

Standard requestHistory missing pagination

Problem

getRequestHistoryStandard in src/tools/requestHistory.ts doesn't follow nextLink pagination when listing request histories.

Impact

If an action has more than 100 HTTP request history entries (e.g., many retries), only the first page is returned.

Solution

Use workflowMgmtRequestAllPages instead of workflowMgmtRequest for the list endpoint.

Files

src/tools/requestHistory.ts lines 164-168

Part of #89

Read the thread · 2026-01-07 · closed · 1 comment

Most recent

feat: add diagnose_run compound diagnostic tool

Add `diagnose_run` compound diagnostic tool

Problem

Diagnosing a failed workflow run currently requires 4-6 sequential API calls:

1. search_runs(status='Failed')        → Find the failure
2. get_run_details(runId)              → Get error summary
3. get_run_actions(runId)              → Find which action failed
4. get_action_io(runId, actionName)    → Get inputs/outputs
5. get_expression_traces(...)          → If expression issue
6. get_action_request_history(...)     → If HTTP conne

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/128) · 2026-01-09 · open · 0 comments

### feat: add duration field to action responses

# Add `duration` field to action responses

## Problem

When debugging performance issues or understanding workflow execution, users need to know how long each action took. Currently, `get_run_actions` returns `startTime` and `endTime` separately, requiring manual calculation.

For diagnostic purposes, having pre-calculated duration:
- Makes slow actions immediately visible
- Enables sorting/filtering by duration
- Reduces cognitive load during debugging

## Proposed Solution

Add a computed `du

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/127) · 2026-01-09 · open · 0 comments

### feat: add status filter parameter to get_run_actions

# Add `status` filter parameter to `get_run_actions`

## Problem

When diagnosing a failed workflow run, users need to find which action(s) failed. Currently, `get_run_actions` returns **all** actions in a run, which can be 50+ actions for complex workflows. The AI assistant or user must then filter client-side to find failures.

This wastes:
- API bandwidth (fetching unnecessary data)
- Token context (large responses consume LLM tokens)
- Time (multiple round-trips if paginated)

## Proposed So

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/126) · 2026-01-09 · open · 0 comments

### Knowledge tools use synchronous file reads

## Problem
Knowledge tools in `src/tools/knowledge.ts` use `readFileSync` which blocks the Node.js event loop.

## Impact
While the knowledge files are small, synchronous file I/O is an anti-pattern in async server code and could cause brief stalls under load.

## Solution
Replace `readFileSync` with async `readFile` from `fs/promises` and make the knowledge functions async.

## Files
- `src/tools/knowledge.ts` - `readKnowledgeFile` function

Part of #87

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/116) · 2026-01-07 · open · 0 comments

### azureIdentity.ts module is unused

## Problem
`azureIdentity.ts` exists in `src/auth/` and implements DefaultAzureCredential-based authentication, but the current `tokenManager.ts` uses passthrough-only mode and never imports or uses it.

## Impact
Dead code that may confuse developers. The Azure Identity approach could be useful for local development without requiring token passthrough.

## Options
1. Remove `azureIdentity.ts` if passthrough-only is the intended design
2. Add a config option to use Azure Identity locally (for CL

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/113) · 2026-01-07 · closed · 0 comments

### Add getTriggerHistory pagination for Standard SKU

## Problem
\\getTriggerHistoryStandard\\ in \\src/tools/triggers.ts\\ doesn't follow \\
extLink\\ pagination. While it respects \\\\\, if the API returns more pages, they are ignored.

## Current Behavior
Only the first page of trigger history is returned for Standard Logic Apps.

## Expected Behavior
Follow \\
extLink\\ pagination to fetch all requested entries (up to \\	op\\ limit).

## Files
- \\src/tools/triggers.ts\\ lines 154-169

Part of #88

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/111) · 2026-01-07 · closed · 0 comments

### [Epic] Shared Infrastructure

Shared utilities, caching, error handling, and validation.

## Bugs
- #74 Silent catch block in shared.ts swallows errors
- #76 Cache race condition allows duplicate API calls
- #58 Fix unsafe non-null assertion in clearCache()

## Enhancements
- #7 Add runtime input validation with Zod
- #77 Add memory limits and LRU eviction to caches

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/92) · 2026-01-05 · open · 0 comments

### [Epic] Runs & Debugging

Run history, actions, expressions, repetitions, and debugging tools.

## Bugs
- #69 Standard SKU expression traces fail - missing POST method
- #75 Add pagination support for Standard repetitions
- #81 Inefficient trigger history fetches all pages
- #82 Portal URL generation uses wrong location

## Enhancements
- #51 Add resubmit_run tool for retrying failed runs
- #57 Add duration field to run history responses

[Read the thread](https://github.com/laveeshb/logicapps-mcp/issues/89) · 2026-01-05 · open · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/laveeshb/logicapps-mcp/issues).

Reported issues for logicapps-mcp

Most discussed

Add workflow state to listRunHistory response

Feature Request

Use Case

Current Response

Proposed Response

Files

Cache TTL from settings is not applied

Problem

Impact

Solution

Add get_runs_by_failed_action tool

Feature Request

Use Case

Proposed API

Implementation Notes

testConnection doesn't use retry logic

Problem

Impact

Solution

Files

listSwagger POST endpoints may need empty request body

Problem

Impact

Solution

Files

HTTP mode missing passthrough token injection

Problem

Impact

Solution

Standard run actions missing pagination

Problem

Impact

Solution

Files

Standard requestHistory missing pagination

Problem

Impact

Solution

Files

Most recent

feat: add diagnose_run compound diagnostic tool

Add diagnose_run compound diagnostic tool

Problem

Add `diagnose_run` compound diagnostic tool