Updated defer in the dbt Cloud IDE docs

website/docs/docs/cloud/about-cloud-develop-defer.md

@@ -35,12 +35,16 @@ When using defer, it compares artifacts from the most recent successful producti
 
 ### Defer in the dbt Cloud IDE
 
+For deferral in the IDE, a deploy job must have run in either the Staging environment (if it exists) or, if not, the Production environment. 
+
+Therefore, when using defer in the IDE, it should fail if a Staging environment exists but no deploy job has run there. Metadata from Staging is unusable unless a deploy job has run successfully.
+
 To enable defer in the dbt Cloud IDE, toggle the **Defer to production** button on the command bar. Once enabled, dbt Cloud will:
 
-1. Pull down the most recent manifest from the Production environment for comparison
+1. Pull down the most recent manifest from the Staging or Production environment for comparison
 2. Pass the `--defer` flag to the command (for any command that accepts the flag)
 
-For example, if you were to start developing on a new branch with [nothing in your development schema](/reference/node-selection/defer#usage), edit a single model, and run `dbt build -s state:modified` —  only the edited model would run. Any `{{ ref() }}` functions will point to the production location of the referenced models.
+If you were to start developing on a new branch with [nothing in your development schema](/reference/node-selection/defer#usage), edit a single model, and run `dbt build -s state:modified` —  only the edited model would run. Any `{{ ref() }}` functions will point to the staging or production location of the referenced models.
 
 <Lightbox src="/img/docs/dbt-cloud/defer-toggle.jpg" width="100%" title="Select the 'Defer to production' toggle on the bottom right of the command bar to enable defer in the dbt Cloud IDE."/>