GCP-Organization Discovery: Incorrect Project ID in Discovery Pattern Launcher Parameters Causes Authorization and Resource Not Found ErrorsIssue 1.GCP Organization Discovery is failing during execution with the following errors in the pattern steps: -403 Forbidden / PERMISSION_DENIED -404 Not Found / Cloud Resource Not Found 2.This occurs despite valid credentials being configured in the discovery schedule.Symptoms 1.GCP Organization Discovery using the pattern "GCP Organization" fails. 2.Pattern step 6 Create resource table fails with: Cloud authorization failed. Check access rights and proper permissions for requested resource. Status: 403 - PERMISSION_DENIED 3.Step 19 Get organizations information fails with: Status: 404 - Cloud Resource Not Found 5.Step 20 Populate cmdb_ci_cloud_org table fails and results in an empty payload. Discovery logs show: MISSING_MATCHING_ATTRIBUTES: In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_cloud_org]. ReleaseAny releaseCause1.In the Discovery Schedule's Pattern Launcher Parameters, the customer might provide the Organization ID in the cloud_account_id field instead of the required Project ID. 2.The pattern GCP Organization expects a valid GCP Project ID under the cloud_account_id parameter. 3.Providing the Organization ID leads to: 4.Step 6 failure with a 403 PERMISSION_DENIED due to invalid access context. 5.Step 8 fails to set the orgId (returns null). 6.Step 19 attempts to query the organization using an empty ID, causing a 404 Cloud Resource Not Found. This misconfiguration breaks the pattern flow and results in no data being populated for cmdb_ci_cloud_org.ResolutionTo fix the issue: 1.Open the affected GCP Organization Discovery schedule in ServiceNow. 2.In the Discovery Pattern Launcher Parameters, ensure that the field cloud_account_id is set to the GCP Project ID, not the Organization ID. ❌ Incorrect: Organization ID (e.g., 123456789012) ✅ Correct: Project ID (e.g., my-gcp-project-001) 3.Save the schedule and re-run the discovery. 4.Once the correct Project ID is configured, the pattern should be able to: -Authorize API requests successfully. -Retrieve the required organization data and subsequent data.