A failed deployment usually points to a specific stage that needs attention. Open the project’s deployment history and select the newest attempt so you can see its status and build output together.
Read the first useful error
Start near the first error in the build output, not the final summary. Later messages often repeat the original failure. Check whether the project can install its dependencies and whether the configured build command completes successfully.
Check project settings
Confirm the selected source, build command, and output directory match the project. A mismatch can produce a successful build with nothing useful to publish, or prevent the build from starting at all. Review any required environment settings without sharing secrets in logs or support messages.
Separate publishing from the domain
First confirm that the deployment itself completed and has a working preview. Then check that the intended domain is attached to that project and that its DNS records match the values shown in the domain settings. DNS changes can take time to become visible.
If the next attempt still fails, compare its first error with the previous one and include the deployment identifier when you contact support. That makes it easier to focus on the failing stage.
Frequently asked questions
What should I check first?
Open the latest deployment and inspect the first failing message in its build output.
The deployment works but my domain does not. What now?
Check the domain attachment and compare the current DNS records with the values shown in its settings.