If your resource fails to provision, you can retry from the resource detail page.
Check the events
Before retrying, review the Events tab on the resource detail page. It shows which provisioning step failed and often includes error details.
Common failure causes:
| Cause | What to do |
|---|
| Temporary infrastructure issue | Retry — usually succeeds on the second attempt |
| Resource quota exceeded | Check your subscription plan |
| Network timeout | Retry after a few minutes |
Retry provisioning
- Go to the resource detail page
- In the quick actions sidebar, click Retry Provisioning
- CodeWire re-runs the full provisioning process
The resource returns to Provisioning state and you can track progress in the Events tab.
Force reprovision (running resources)
If your resource is already running but in a stuck or corrupted state, use Force Reprovision instead. This tears down the application deployment and re-runs the full provisioning pipeline while preserving your data.
If your resource is running and you need to re-apply configuration (for example, after changing GitHub integration or login provider settings):
- Go to the resource detail page
- Click Force Reprovision in the sidebar
- CodeWire re-applies the configuration
Force reprovisioning briefly interrupts access to your Coder instance while configuration is re-applied.
Still failing?
If provisioning continues to fail after retrying, the Events tab provides detailed error information. Contact support with the event details for assistance. 
