Skip to content

tasks: improve error visibility when workspace provisioning fails #19766

Closed

Description

@blink-so

Problem

When workspace provisioning fails during task creation, the failure is not evident from the Tasks UI. Users see a task that appears to be in progress or stuck, but cannot easily determine that the underlying workspace build has failed.

Image

This creates a poor user experience where:

  • Users wait indefinitely for tasks that will never complete
  • No clear indication of what went wrong
  • Users must navigate away from the task UI to debug issues

Current Behavior

  • Task UI shows indeterminate progress
  • No indication of provisioning failure
  • No link to workspace or build logs
  • Users cannot troubleshoot directly from task interface

Expected Behavior

  • Clear error state when provisioning fails
  • Direct link to failed workspace build
  • Access to build logs from task UI
  • Clear messaging about what failed and next steps

Proposed Solution

Extend the task UI to:

  1. Display clear error states for failed provisioning
  2. Show link to associated workspace when available
  3. Provide access to workspace build logs inline or via link
  4. Show helpful error messages and recovery options

Related Work

This builds on that work but focuses on failure cases and error visibility.

Activity

  1. added theissue type on Sep 10, 2025
  2. BrunoQuaresma commented on Oct 15, 2025

    @BrunoQuaresma
    Contributor

    I’m not able to reproduce it, and looking at the code, it seems to be already handled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions