Deployment Status is a monitoring screen, not something you create. Here is how to use it to watch a deployment through and act on the result.
- Open the page
From Setup, type Deployment in the Quick Find box and select Deployment Status. The list loads with any in-progress, pending, and completed deployments from roughly the last 30 days.
- Watch a live deployment
For a deployment that is running, read the two progress charts: one for component processing and one for Apex test execution. The test chart is your early signal for whether a production deploy will clear the 75 percent coverage gate.
- Check the result and open details
Once it lands in the completed section as Succeeded or Failed, click View Details on a failure to see per-component results and the exact error messages. Fix the named components and redeploy.
- Quick Deploy a fresh validation
If you validated first and the validation is still within its window, use Quick Deploy on that entry to commit without re-running tests. Confirm the validation completion time before relying on it.
Expands an in-progress or completed deployment to per-component status and full error text, the actionable debugging surface for failures.
Stops a queued or in-progress deployment. Clean for queued jobs; an in-progress cancel aborts as safely as the platform can but may not be instant.
Commits a recently validated component set without re-running Apex tests, available when the validation succeeded within the documented window and covers the same components.
- History is kept only for about 30 days. Export details you need to keep before the entry ages off the list.
- The 75 percent Apex coverage rule is enforced on production deploys only, so a deploy that passed in a sandbox can still fail in production.
- A Quick Deploy validation that is older than its window has expired; the deploy then runs the full test cycle when you least expect it.
- Only one deployment runs to an org at a time. A second deploy queues as Pending instead of running in parallel.