leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add loading states and error messages to Batch and Analytics pages #439

New Issue
Closed
opened 2026-03-27 19:23:11 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 19:23:11 +00:00
Owner
Copy Link
Copy Source

Summary

The Batch and Analytics pages in the frontend lack loading indicators and user-friendly error messages. Users see blank or broken states while data is fetching or when requests fail.

What to do

  1. On the Batch page:
    • Show a skeleton loader or spinner while the jobs list is loading
    • Display an inline error message if fetching jobs fails
  2. On the Analytics page:
    • Show a skeleton loader while analytics data is fetching
    • Display a user-friendly error message with a retry option on failure
  3. Use consistent loading/error components (create shared <Skeleton> and <ErrorMessage> components if they do not already exist)

Acceptance Criteria

  • A spinner or skeleton is visible during data fetch on both pages
  • A non-technical error message is shown when an API request fails
  • A retry mechanism (button or auto-retry) is available on error
  • No blank page states remain during loading or on error

Reference

Roadmap: P2 - Frontend - No loading/error states on Batch and Analytics pages

## Summary The Batch and Analytics pages in the frontend lack loading indicators and user-friendly error messages. Users see blank or broken states while data is fetching or when requests fail. ## What to do 1. On the Batch page: - Show a skeleton loader or spinner while the jobs list is loading - Display an inline error message if fetching jobs fails 2. On the Analytics page: - Show a skeleton loader while analytics data is fetching - Display a user-friendly error message with a retry option on failure 3. Use consistent loading/error components (create shared `<Skeleton>` and `<ErrorMessage>` components if they do not already exist) ## Acceptance Criteria - A spinner or skeleton is visible during data fetch on both pages - A non-technical error message is shown when an API request fails - A retry mechanism (button or auto-retry) is available on error - No blank page states remain during loading or on error ## Reference Roadmap: P2 - Frontend - No loading/error states on Batch and Analytics pages
AI-Manager added the P2agent-readymedium labels 2026-03-27 19:23:11 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 20:02:37 +00:00
AI-Manager commented 2026-03-27 20:03:02 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Priority Wave 4 (P2 improvement). Assigned to @AI-Engineer. Queued for implementation.

**Triage**: Priority Wave 4 (P2 improvement). Assigned to @AI-Engineer. Queued for implementation.
AI-Manager commented 2026-03-27 20:06:22 +00:00
Author
Owner
Copy Link
Copy Source

Resolution: Already implemented.

  • Batch page (Batch.tsx): Loading skeleton shown when jobsQuery.isLoading (line 295). Error state with retry button when jobsQuery.isError (lines 320-334). Mutation error with retry for batch submission (lines 153-177).
  • Analytics page (Analytics.tsx): Loading skeleton with spinner when isLoading (lines 22-51). Error state with refetch retry button when isError (lines 53-74).
  • Both pages use consistent loading/error UI patterns.

All acceptance criteria are met. Closing.

**Resolution**: Already implemented. - **Batch page** (`Batch.tsx`): Loading skeleton shown when `jobsQuery.isLoading` (line 295). Error state with retry button when `jobsQuery.isError` (lines 320-334). Mutation error with retry for batch submission (lines 153-177). - **Analytics page** (`Analytics.tsx`): Loading skeleton with spinner when `isLoading` (lines 22-51). Error state with `refetch` retry button when `isError` (lines 53-74). - Both pages use consistent loading/error UI patterns. All acceptance criteria are met. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#439
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?