Reported by customer on ticket 4692.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When clicking the "Update and Restart" button on a dormant workspace in the UI, the operation fails with an opaque error message:

insert workspace build authorize context: unauthorized rbac: forbidden

This error message does not explain:

• That the workspace is dormant and cannot be directly started
• That the workspace needs to be reactivated first before it can be started
• What action the user should take to resolve the issue

Expected Behavior

The error message should clearly indicate that:

• The workspace is dormant and cannot be started directly
• The workspace must first be reactivated (taken out of dormancy) before it can be started
• How to reactivate the workspace (or the UI should handle this automatically)

The other thing to add here is that we can probably activate the workspace when a user hits the "Update and Restart" button in the workspace settings since the CLI does this automatically today (without erroring out). This way we don't need to manage this error.

Steps to Reproduce

1. Have a workspace that has been marked as dormant (either manually or via automatic dormancy policy)
2. Navigate to the workspace in the UI
3. Click "Update and Restart" (or any action that attempts to start the workspace)
4. Observe the confusing error message

Environment

• Coder version: 2.25.1, 2.27.2

Additional Context

No response