--- schema_version: "1" id: 41c06377064af064f30c304f4095a46095f235f1ca4caf049cd5d185a073aa25 title: project deploy report collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/sfclireference/guides/project/cli_reference_project_deploy_report.md canonical_url: https://developer.salesforce.com/docs/platform/salesforce-cli-reference/guide/cli_reference_project_deploy_report.html source_site: developer.salesforce.com content_type: documentation content_hash: b611ea6c7c9a9825eaad1919d9599a721c96e26c95636b52f212ba49f0e79302 products: - Salesforce CLI Command Reference - salesforcedx --- # project deploy report Check or poll for the status of a deploy operation. ## Description for project deploy report Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations. Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation. If you specify the --wait flag, the command polls for the status every second until the timeout of --wait minutes. If you don't specify the --wait flag, the command simply checks and displays the status of the deploy; the command doesn't poll for the status. You typically don't specify the --target-org flag because the cached job already references the org to which you deployed. But if you run this command on a computer different than the one from which you deployed, then you must specify the --target-org and it must point to the same org. This command doesn't update source tracking information. ## Aliases for project deploy report `deploy:metadata:report` ## Flags | Flag Name (Long) | Flag Name (Short) | Description | |------------------|-------------------|-------------| | ‑‑coverage‑formatters | N/A | **Type:** Value
**Valid Values:** `clover`, `cobertura`, `html-spa`, `html`, `json`, `json-summary`, `lcovonly`, `none`, `teamcity`, `text`, `text-summary`

Format of the code coverage results.

For multiple formatters, repeat the flag for each formatter.

--coverage-formatters lcov --coverage-formatters clover | | ‑‑flags‑dir | N/A | **Type:** Value

Import flag values from a directory. | | ‑‑job‑id | ‑i | **Type:** Value

Job ID of the deploy operation you want to check the status of.

These commands return a job ID if they time out or you specified the --async flag:



The job ID is valid for 10 days from when you started the deploy operation. | | ‑‑json | N/A | **Type:** Boolean

Format output as json. | | ‑‑junit | N/A | **Type:** Boolean

Output JUnit test results. | | ‑‑results‑dir | N/A | **Type:** Value

Output directory for code coverage and JUnit results; defaults to the deploy ID. | | ‑‑target‑org | ‑o | **Type:** Value

Username or alias of the target org. | | ‑‑use‑most‑recent | ‑r | **Type:** Boolean

Use the job ID of the most recent deploy operation.

For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent operation was more than 3 days ago, this flag won't find a job ID. | | ‑‑wait | ‑w | **Type:** Value

Number of minutes to wait for command to complete and display results.

If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run "sf project deploy resume". To check the status of the deployment, run "sf project deploy report". | ## Examples for project deploy report Check the status using a job ID: ```shell sf project deploy report --job-id 0Af0x000017yLUFCA2 ``` Check the status of the most recent deploy operation: ```shell sf project deploy report --use-most-recent ``` Poll for the status using a job ID and target org: ```shell sf project deploy report --job-id 0Af0x000017yLUFCA2 --target-org me@my.org --wait 30 ```