Skip to main content
Force Reprovision is a recovery tool for resources that are stuck or in a bad state. It tears down the application deployment and re-runs the full provisioning pipeline.

​
When to use

Use Force Reprovision when:
  • Your resource shows Running but the Coder dashboard is inaccessible
  • A previous upgrade or provisioning partially failed
  • Standard retry doesn’t resolve the issue
Force Reprovision is a recovery operation. Only use it when other options have failed.

​
What happens

Preserved (your data is safe):
  • Your database (all Coder data: workspaces, templates, users)
  • DNS records
  • Existing workspace data
Recreated (rebuilt from scratch):
  • The Coder application deployment
  • Ingress and routing configuration
  • Admin setup
The Coder instance restarts with the same database, so all your workspaces, templates, and users are intact after reprovisioning.

​
How to force reprovision

  1. Navigate to the resource’s detail page
  2. Click Force Reprovision in the actions menu
  3. Type the resource name to confirm
  4. Click Confirm
The resource enters Provisioning state while the deployment is rebuilt. This typically takes 2-5 minutes.
Force Reprovision requires the owner role in the organization.

​
After reprovisioning

Once complete:
  • The resource returns to Running status
  • Admin credentials remain the same
  • All workspaces and templates are preserved
  • Users can sign in immediately
If the reprovision fails, check the Events tab for details and contact support.

Retry failed provision

For resources that failed during initial provisioning.

Resource statuses

Understanding resource lifecycle states.