Skip to content

Add a timeout + debug steps to the Coder agent (agent stuck in Connecting... forever isn't accurate) #4678

Closed
@bpmct

Description

@bpmct

This is taken from #4201

Step 3. Add a timeout parameter to the coder_agent resource
After the specified duration of inactivity, the UI and CLI would display that something wrong happened. Templates can define a debug_url parameter in their front-matter that can direct users to a help page.

After the timeout, the agent can go from Connecting to Disconnected

This debug_url can be surfaced in the dashboard/CLI to make it easy for admins to troubleshoot a timed-out workspace. For larger deployments, an admin could edit the template README and change debug_url to an internal wiki/chat/ticketing system so users can request help. Perhaps the debug URL could also be surfaced for failed builds as well

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions