Troubleshooting
Start with the four most common failure surfaces.
Check the common failure surfaces
Most Crucible errors come from one of these four surfaces. Start with the runtime that failed, then work down the list.
- Runtime: Find the workspace, lite deployment, or full deployment that failed. The Status column on the project's Deployments and Workspaces tabs shows "Release failed"; open a deployment's Logs tab for detail, and use Redeploy once the cause is fixed. If project setup failed, the project shows "Needs attention" with the failed step's error.
- Auth: Check the deployment's Auth mode in its Settings (Sandbox or Production), and that the person signing in has an account in that environment. Crucible registers sign-in callback URLs for you.
- Configuration: Check the Variables tab for the affected deployment, including values inherited from the project.
- Source: Confirm the Branch the runtime is running and that your latest commit is pushed to it.
Still blocked?
Send the details to the Crucible team with Feedback in Crucible. If an error toast showed an Error ID, copy it into your message.