A clear path forward
Why does my Development Environment fail to build or start?
Find the first failing step before changing the setup. Fetching code, installing packages, running setup and starting the app are different parts of an environment build.
The failed step tells you where to look. If checkout fails with an authentication or authorization error, check the connection and repository permissions used by the build. For other checkout errors, ask Agent to inspect the exact error before changing access.
- Open the build result and keep the first useful error, not only the final “failed” message.
- If fetching a repo fails, check shared workspace access for that repo.
- If package installation or setup fails, check the named command, dependency or required service.
- If the app will not start, ask Agent to inspect its startup logs and server process.
- After fixing the relevant issue, rebuild and check the final result in a fresh sandbox.
When a scheduled rebuild fails, new sandboxes can still use the most recent successful build. That does not mean the latest change built successfully. Keep the build result and the version you tested together.
Was this page helpful?
Still stuck? Try troubleshooting with Agent.
Still stuck? Try troubleshooting with Agent.
Copy this prompt and paste it into Agent. For a project issue, open the project where it happens first. Add what happened and anything you've already tried. Don't include passwords, API keys, database connection strings or payment-card details.
Copying does not open Agent or send a support request. Agent availability and usage depend on your account.
Can't open your project, or need another kind of help? Get help.