Visual Walkthrough: The Complete User Journey
Let's walk through exactly what happens when you use the Logic Apps Local Dev Tools extension with multiple containerized Logic Apps.
Step 1: Open Command Palette
Quick access from your VSCode command palette.
Press Cmd/Ctrl+Shift+P and type "LogicAppRunHistory" to see all available commands.
Available commands:
-
Open Logic Apps Run History Panel- Open the main panel (we'll use this one) -
Reopen Last Run History Panel- Quickly reopen with cached endpoints -
Detect Logic Apps Runtime and Azurite- Auto-detect running instances -
Clear Cached Endpoints- Reset endpoint cache
Step 2: Enter Your Logic Apps Endpoints
Provide URLs of all your Logic Apps containers.
After selecting "Open Logic Apps Run History Panel", you'll be prompted to enter your Logic Apps endpoint URLs. You can enter multiple endpoints separated by commas to see all containers in one view.
Example:
http://localhost:7071/runtime/, http://localhost:8071/runtime/, http://localhost:9071/runtime/
Or simply press Enter to use the endpoints configured in your VSCode settings.
Pro tip: The extension remembers your last-used endpoints, so next time you can use "Reopen Last Run History Panel" to skip this step!
Step 3: Logic Apps Instances Overview
The unified dashboard showing all your containers in one view.
Once connected, you immediately see all your Logic Apps containers (running on different ports) in a single overview. No more switching between terminals or trying to remember which port runs which Logic App.
What you see:
- All containers at once (ports 7071, 8071, 9071, etc.)
- Total workflow counts for each instance
- Health status for each instance
- Enabled/disabled workflow counts
- Stateful vs. stateless distribution
- Click any instance to see its workflows
Step 4: Instance Details with Workflow Metadata
Click on any instance to see detailed workflow information.
From the instances overview, click on any instance to drill down into its workflows. Each Logic App instance shows you rich metadata about every workflow - no need to open files or check logs.
What you see:
- Workflow names and types (Stateful/Stateless)
- Trigger information (HTTP, Recurrence, etc.)
- Health status and enabled/disabled state
- One-click "Get URL" buttons for HTTP triggers
- "View Runs" button to see execution history
Step 5: Run History and Action Details
Browse run history and inspect each action's inputs/outputs.
From the workflow details, click "View Runs" to see all executions. Then click on any specific run to see every action that executed, with full input/output payloads.
What you see:
- List of all runs with status (Succeeded, Failed, Running)
- Timestamps and duration
- Action-by-action breakdown
- Input and output payloads for each step
- Error messages for failed actions
- No Storage Explorer needed - everything is formatted and ready to view
Step 6: Flow Diagram and Deep Debugging
Flow tree view summarizes the workflow, detailed breakdown shows everything.
For complex workflows with many actions, the run details page shows two complementary views:
What you see:
Top Section - Flow Diagram (Tree View Summary):
- Text-based tree visualization - Quick overview of workflow structure
- Status indicators - 🟢 Succeeded, 🔴 Failed, ⚪ Skipped
- Execution duration - See how long each step took
- Hierarchical layout - Shows parent-child relationships (Scopes, Loops, Conditions)
- Perfect for getting a quick understanding of what happened
Bottom Section - Detailed Action-by-Action Breakdown:
- Full action details - Click any action to see inputs/outputs
- Collapsible sections - Expand/collapse to reduce scrolling
- Loop iterations - Click "View All Iterations" to expand ForEach/Until loops
- Nested containers - Scopes, Conditions, Switch cases properly organized
- Payload links - Direct access to input/output JSON for each action
The combination is powerful: The flow tree gives you the big picture at a glance, while the detailed breakdown lets you dig into specific actions with actual runtime data - similar to the experience you get in the Azure Portal, but right inside VS Code.
Bonus: Working with Multiple Containers
Managing multiple containerized Logic Apps made easy.
The beauty of this extension is that whether you're running 2 containers or 10, everything is accessible from one unified interface. No more juggling terminals, docker commands, or storage explorer windows.
What you see:
- Multiple Logic Apps instances from different containers
- Clear separation between instances
- Quick navigation between containers
- All the information you need without Docker commands
Key Features Recap
✅ Unified Dashboard - All containers in one view
✅ Rich Metadata - See workflow types, triggers, health status
✅ One-Click URLs - Get callback URLs instantly
✅ Run History Browser - See all executions with status
✅ Payload Viewer - Formatted inputs/outputs, no JSON parsing
✅ Flow Diagrams - Visual execution paths
✅ Collapsible UI - Manage complex workflows easily
✅ Loop Debugging - Expand iterations for ForEach/Until
✅ Command Palette - Quick access to all features
Ready to Try It?
Install: Search for "Logic Apps Local Dev Tools" in VSCode marketplace
Get Started:
- Install the extension
- Run your Logic Apps in Docker (port 7071)
- Run Azurite storage emulator
- Open the extension - see everything instantly!
Top comments (0)