[Initial Testing] Workflow Execution Visibility & UX Issues

Testing Overview

  • Time spent: ~2 hours
  • Workflow built: Webhook → AI Agent → Conditional Branching → HTTP Actions
  • Focus: General usability, AI Agent functionality, execution debugging

What Worked Well

:white_check_mark: Drag-and-drop interface - intuitive node placement and connection
:white_check_mark: AI Agent node - successfully classified messages without requiring API keys (impressive!)
:white_check_mark: Data picker - easy to reference previous step outputs
:white_check_mark: Workflow activation via “Live” toggle works once discovered


Issues Found

1. AI Agent Executions Tab Shows “No Recent Data”

Description: AI Agent processes successfully (green checkmark), but Executions tab displays “No Recent Data”

Expected: Should show execution history with inputs/outputs for debugging

Steps to reproduce:

  1. Create workflow: Webhook → AI Agent → Condition
  2. Send POST request to webhook
  3. AI Agent executes (green checkmark appears)
  4. Click AI Agent → Executions tab
  5. Result: “No Recent Data”

Impact: Cannot debug AI Agent behavior or verify classification output


2. Unclear Workflow Activation Process

Description: Workflow shows “Triggers inactive. Manual runs only.” but no obvious way to activate

What I found: “Live” toggle exists next to workflow name (top left) but is easy to miss

Suggestion: Add more prominent “Activate Workflow” button or banner when triggers are inactive


3. Auto-Created HTTP Nodes Cannot Be Configured

Description: When adding action to Condition’s “Then go to” branch, platform auto-creates “Send POST Request” node but configuration panel doesn’t load or is inaccessible

Workaround: Delete auto-created node and manually add HTTP node via canvas

Impact: UX friction when building conditional workflows


4. Condition Configuration Resets When Adding Actions

Description: After configuring IF condition, clicking “Select step” to add action clears the IF configuration

Impact: Must re-configure condition after adding actions


5. Limited Execution Trace Visibility

Description: Unable to see full workflow execution trace across all nodes in single view

Expected: Unified execution view showing data flow through all steps (like n8n’s execution view)

Current: Each node’s Executions tab shows isolated data

Impact: Difficult to debug multi-step workflows or verify branching logic


Questions

  1. Is there a way to view full execution traces across all nodes?
  2. Is the AI Agent Executions tab issue a known bug?
  3. Are there plans to improve trigger activation UX?
  4. What’s the recommended way to debug conditional branching when execution data isn’t visible?

Overall Impression

GetGlow has strong potential, especially the AI Agent with built-in MCP tools. Main pain points are around execution visibility and debugging multi-step flows. With better execution tracing and clearer activation controls, this could be very competitive.

Happy to provide more details or test specific scenarios.

Thanks for your report. All the mentioned issues are tracked and we’re working on them.

Improvements to execution and data visibility within workflows are also in progress and prioritized for the upcoming sprints.