Add 2 troubleshooting tips for issues encountered by CEs (#572)

* Revert to gerund

Though the style guide says to just use imperatives, "get started" just sounds weird. Also this is more consistent with "troubleshooting"

* merge

* merge

* stable release

* removed reference to fork

* updated procedures

* wee corrections

* recorrect

* wee changes

* wee changes

* remove branch sync procedures

* corrections from Hannah

* first revisions

* more revisions

* more work

* first cut of variable-per-column rewrite

* more work

* more work

* more work

* restore changes

* more changes

* more changes

* more changes

* more changes

* updates to json spec

* more edits

* multiple directories

* more changes

* more changes

* more edits

* remove headings from TOC

* minor edits

* more edits

* remove wrong image reference

* remove more headings from TOC

* revisions per Ajai and a new diagram

* remove image, replace by text

* mention that node and field order in MCF do not matter

* added mention of required option for subdirs

* added note about MCF

* move feedback from index page to FAQ

* added info on stat var groups

* wee fixes

* make feedback links nicer

* added detail about measuredProperty in variable per column

* fix typo

* revert output directory change

* fixed observation properties to refer to observations, not variables

* correct erroneous statement about data

* revert change

* Updating Data Sources pages

* Updating Data Sources pages

* added 2 more troubleshooting tips based on CE experience

* revert changes to local client

custom_dc/troubleshooting.md

@@ -85,17 +85,23 @@ If you try to enter input into any of the explorer tools fields, and you get thi
 
 This is because you are missing a valid API key or the necessary APIs are not enabled. Follow procedures in [Enable Google Cloud APIs and get a Maps API key](/custom_dc/quickstart.html#maps-key), and be sure to obtain a permanent Maps/Places API key.
 
-## Terraform problems
+## Terraform setup problems
 
 ### "Error: Error when reading or editing...oauth2: "invalid_grant" "reauth related error (invalid_rapt)""
 
-If you are trying to run `terraform plan` or `terraform apply` and it fails with an error like this:
+This is due to expired credentials. Generate new credentials as described in [Generate credentials for Google Cloud authentication](deploy_cloud.md#gen-creds). You may also configure the frequency with which credentials must be refreshed; see <https://support.google.com/a/answer/9368756>{: target="_blank"} for details.
 
-```
-Error: Error when reading or editing Network Not Found : default: Get "https://compute.googleapis.com/compute/v1/projects/datcom-website-dev/global/networks/default?alt=json&prettyPrint=false": oauth2: "invalid_grant" "reauth related error (invalid_rapt)" "https://support.google.com/a/answer/9368756"
-```
+### "Error: Error applying IAM policy for cloudrun service ..." 
 
-This is due to expired credentials. Generate new credentials as described in [Generate credentials for Google Cloud authentication](deploy_cloud.md#gen-creds). You may also configure the frequency with which credentials must be refreshed; see <https://support.google.com/a/answer/9368756>{: target="_blank"} for details.
+This indicates that the project for which you are trying to create resources has an organizational policy that prevents resource creation, such as domain resource sharing constraints. To remedy this:
+1. Go to <https://console.cloud.google.com/iam-admin/orgpolicies/list>{: target="_blank"} for your project and click **View active policies**.
+1. Check to see if there is a policy with a constraint that interfers with resource creation (e.g. `iam.allowedPolicyMemberDomains`). 
+1. Edit the policy to remove the relevant constraint.
+1. Rerun Terraform.
+
+### "Error: Error waiting to create Job...timeout while waiting for state to become 'done: true'"
+
+This is likely a transient issue; try exiting and rerunning Terraform.
 
 ## Cloud Run Service problems