task status is empty when workspace is starting or startup script is running #1063

Activity

1. mtojek

   assigned

   DanielleMaywood

   and

   ssncferreira

   and unassigned

   DanielleMaywood

   on Oct 22, 2025
2. mafredri commented on Oct 24, 2025

   

   mafredri

   on Oct 24, 2025

   Member

   More actions

   With the new tasks data model refactor, the GET /api/experimental/tasks response contains Task.Status which will be initializing during the mentioned state, once ready it will be active.
3. johnstcn commented on Oct 24, 2025

   

   johnstcn

   on Oct 24, 2025

   Member

   More actions

   FWIW I think in this case Ben is mentioning the empty "Agent status" field (a.k.a. TaskState).
4. ssncferreira commented on Nov 12, 2025

   

   ssncferreira

   on Nov 12, 2025

   Last edited by ssncferreira

   More actions

   As mentioned in the previous comments, with the new tasks data model, when a task is initializing, an "Initializing" status appears. However, since the agent is still waiting for workspace initialization or is still initializing, its state (current_state) is set as null, and the message "No message available" is displayed, which is not very informative about what's actually happening during initialization.

   

   The solution presented in coder/coder#20692 consists of adding more descriptive messages that explain the initialization workflow, such as: "Workspace is pending" > "Workspace is starting" > "Agent is connecting" > "Agent is starting" > "App is initializing"

   This provides users with clear, actionable feedback about the current initialization phase.

   
5. ssncferreira

   closed this as completedin coder#20692on Nov 17, 2025
6. ssncferreira

   added a commit that references this issue on Nov 17, 2025

   fix: set codersdk.Task current_state during task initialization (#20692)

   ...

   16b8e60