>_
.issue.db
/highway-workflow-engine
Dashboard
Issues
Memory
Lessons
Audit Log
New Issue
Edit Issue #674
Update issue details
Title *
Description
Problem: For long-running workflows, users are blind to progress during execution. They have to poll multiple endpoints. Findings from investigation: - Activity workers work correctly for parallel long-running tasks - Rich data IS available in DB but not exposed efficiently Current state: - GET /workflows/{id} shows status but not current_step or progress - GET /workflows/{id}/events shows step-by-step events (separate call needed) - GET /workflows/{id}/activities shows activity status (separate call needed) Proposed additions to GET /workflows/{id}: 1. current_step - which step is currently executing/sleeping 2. progress.completed_steps / total_steps / percentage 3. activities_summary - inline activity status summary 4. last_event - most recent event type and timestamp Also: - Fix activity_name showing as 'activity' instead of task_id - Add activity_started event when activity worker claims task - Consider SSE endpoint for real-time updates
Priority
Low
Medium
High
Critical
Status
Open
In Progress
Closed
Won't Do
Due Date (YYYY-MM-DD)
Tags (comma separated)
Related Issues (IDs)
Enter IDs of issues related to this one. They will be linked as 'related'.
Update Issue
Cancel