LARunHistoryNavigator

This Repo to capture user feedback and track issue.

Logic Apps Local Dev Tools

This VS Code extension streamlines local development and debugging for Azure Logic Apps Standard projects running in Docker or locally.

Features

• Multi-Endpoint Support: Connect to multiple Logic Apps runtime endpoints simultaneously
• Enhanced Workflow Metadata: View workflow kind (Stateful/Stateless), triggers, health status, and enabled/disabled state
• Trigger Callback URLs: Get HTTP trigger callback URLs with one click (automatically replaces internal container URLs)
• Instance Overview: See detailed statistics for each Logic Apps instance (workflow counts, health status, etc.)
• Detect and connect to a local Logic Apps Standard runtime (Docker or host)
• One-click command to open the backend Logic Apps UX experience, preconfigured to the correct runtime URL
• Validate reachability of your Logic Apps management API endpoint in one click
• Custom panel/webview to show run history and workflow details using the Logic Apps management API
• Automatically retrieves the local host master key when needed (or respect a key you configure manually)
• View input and output for each workflow action (shape) by clicking on a run
• Simplified Azurite connection string management

Requirements

• Logic Apps Standard runtime (local host or container) exposing the management API
• Optional: LogicAppsUX Standalone designer (see https://github.com/Azure/LogicAppsUX) for authoring
• Node.js and npm

Usage

1. Start your Logic Apps Standard runtime(s) and Azurite (host or Docker)
2. Open your project in VS Code
3. Use the command palette (Cmd/Ctrl+Shift+P) and search for:
   • Detect Logic Apps Runtime and Azurite
   • Validate Logic Apps Management API
   • Open Backend Logic Apps UX
   • Open Logic Apps Run History Panel
4. When opening the Run History Panel, you'll be prompted to enter endpoints:
   • Enter multiple endpoints separated by commas: http://localhost:7071/runtime/, http://localhost:9898/runtime/
   • Leave blank to use configured endpoints from settings
   • The extension will connect to all endpoints in parallel
5. If the management API requires authorization, the extension auto-fetches the local host master key (/_master); you can also set a specific key via settings
6. In the run history panel, click on a run to view input/output for each action or refresh the list as needed

Multi-Endpoint Support (New)

This extension now supports connecting to multiple Logic Apps endpoints simultaneously. This is useful when you have:

• Multiple Logic Apps runtimes running on different ports
• Different environments (dev, staging) running locally
• Containerized Logic Apps with different port mappings

How it works:

1. Configure Endpoints: Set multiple endpoints in settings or provide them when prompted
2. Parallel Connection: The extension connects to all endpoints in parallel for fast loading
3. Unified View: All instances from all endpoints appear in a single overview panel
4. Smart Routing: Each workflow operation automatically uses the correct endpoint

Instances Overview

The run history panel shows an enhanced "Instances" overview where you can:

• View all Logic Apps instances from all connected endpoints
• See detailed instance statistics:
  • Total workflow count
  • Enabled/Disabled workflow counts
  • Stateful/Stateless workflow counts
  • Healthy workflow count
  • Host URL and fetch timestamp
• Open an instance to see its workflows with detailed metadata
• View workflow triggers and their types
• Get HTTP trigger callback URLs with one click
• Drill into a workflow to view run history and details
• Navigate back through the hierarchy

Workflow Details

When viewing workflows in an instance, you can see:

• Workflow Kind: Stateful or Stateless
• Status: Enabled or Disabled
• Health State: Healthy or Unhealthy
• Triggers: View all triggers with their types (HTTP, Recurrence, etc.)
• Callback URLs: For HTTP triggers, click "Get URL" to retrieve the callback URL
  • URLs are automatically adjusted for container environments (replaces internal hostnames with public endpoints)

Use the "Open Logic Apps Run History Panel" command to see the instances overview.

Extension Settings

The extension contributes the following settings (Command Palette → Preferences: Open Settings (UI)):

• logicAppsLocalDevTools.managementApi.endpoints: [New] Array of Logic Apps runtime endpoints. The extension will connect to all endpoints. Example: ["http://localhost:7071/runtime/", "http://localhost:9898/runtime/"]
• logicAppsLocalDevTools.managementApi.baseUrl: [Deprecated] Single base URL for the local Logic Apps runtime (default: http://localhost:7071/runtime/). Use endpoints instead for multi-endpoint support. The extension appends webhooks/workflow/api/management automatically.

Note about non-Docker setups

If your Logic Apps runtime is not running in Docker or listens on a different host/port, configure the extension setting logicAppsLocalDevTools.managementApi.baseUrl to point to your runtime base (for example: http://my-host:7071/runtime/ or http://127.0.0.1:7071/runtime/). The extension's runtime detection and the "Open Backend Logic Apps UX" flow will prefer this configured host as a fallback instead of assuming localhost.

• logicAppsLocalDevTools.managementApi.apiVersion: API version appended to every management API request (default: 2016-06-01)
• logicAppsLocalDevTools.managementApi.apiKey: Optional function/system key to append as code and x-functions-key for secured endpoints
  • Leave empty to let the extension retrieve the local _master key automatically via /admin/host/systemkeys/_master

Known Issues

• Workflow trigger and run result commands are placeholders

Release Notes

0.0.2

• Enhanced Workflow Metadata: Added workflow kind (Stateful/Stateless), trigger information, enabled/disabled status, and health state
• HTTP Trigger Callback URLs: Click "Get URL" button to retrieve callback URLs for HTTP triggers
• Automatic URL Replacement: Internal container URLs are automatically replaced with public endpoints
• Enhanced Instance Overview: Display detailed statistics including workflow counts, stateful/stateless counts, and health metrics
• Improved UI: Better visual presentation of workflow details with badges and status indicators
• API Updates: Uses correct /listCallbackUrl endpoint with POST method and API version 2018-11-01

0.0.1

• Initial release: runtime detection, designer launch, run history panel with drill-in
• Multi-endpoint support for connecting to multiple Logic Apps instances
• Instances overview with workflow grouping
• Run history navigation and action I/O viewing

---

Developer: build & test locally

From the repository root:

# install dependencies
npm install

# compile TypeScript
npm run compile

# run unit tests (fast, Node-only)
npm run test:unit

# package a VSIX (requires @vscode/vsce)
npx @vscode/vsce package

Install the packaged VSIX

# install the VSIX into your locally running VS Code (macOS/Linux)
code --install-extension /path/to/logic-apps-run-history-view-tool-0.0.1.vsix

# force reinstall/upgrade
code --install-extension /path/to/logic-apps-run-history-view-tool-0.0.1.vsix --force

If the code command is not available, open VS Code and run the Command Palette → "Shell Command: Install 'code' command in PATH".

Troubleshooting:

• If packaging fails, ensure package.json is valid JSON and the extension compiles successfully (npm run compile).
• Unit tests are run with ts-node so they do not require a VS Code test host.

---

Enjoy local Logic Apps development!

---

Screenshots

Below are screenshots of the extension in action:

Workflows List

Run History and Details

Command Palette